GNOME 3.30 was officially released on 5th Sep 2018. This bug is our usual long-term tracking bug.
1. No talks in here.
2. 3.30 will be included in tree when it is ready.
3. Do not file bump request reports, we might be slow but eventually we will
get around all 3.30 bumps. We already know what's missing from various report scripts. Pull Requests with a note here is acceptable and appreciated, especially when doing more work than simple dependency updates (e.g updating to meson where needed), but no guarantees how fast we can review.
4. If you have a particular problem with 3.30 ebuilds, please file a separate
bug report and make it block this one.
As an extra note, there might be individual 3.30 packages appearing much earlier than the core. This may be done during ongoing work on 3.26 and 3.28 when the 3.30 release can safely work in older GNOME (often in case the 3.30 release really only has bug fixes and/or translation updates over the previous big version; sometimes in case of feature updates too when it doesn't depend on other GNOME stack things). This doesn't mean that core of 3.30 is about to get included as well at that point, unfortunately.
*** Bug 665322 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s):
Author: Mart Raudsepp <firstname.lastname@example.org>
AuthorDate: 2019-03-18 11:02:21 +0000
Commit: Mart Raudsepp <email@example.com>
CommitDate: 2019-03-18 11:02:21 +0000
gnome-base/gnome: bump to 3.30.2
Package-Manager: Portage-2.3.52, Repoman-2.3.12
Signed-off-by: Mart Raudsepp <firstname.lastname@example.org>
gnome-base/gnome/gnome-3.30.2.ebuild | 51 ++++++++++++++++++++++++++++++++++++
1 file changed, 51 insertions(+)
3.30 is mostly removed from tree in favor of stable 3.32. Closing the bug after copying the still open dependent tracking bugs to 3.34 bug 695712