Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2390023 ** Information from BlockerBugs App:
The votes have been last counted at 2025-09-01 15:35 UTC and the last processed comment was #comment-984065
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
GDM is obviously an important part of Gnome. Without it user will have a hard time logging in so does seem to violate https://fedoraproject.org/wiki/Basic_Release_Criteria#Expected_installed_system_boot_behavior
Please note that this bug is about GNOME 49 Beta which is currently not in F43. It is proposed with this justification:
The gnome stack is important to have up to date and not having this fixed will prevent GDM/mutter/Gnome-shell being their latest versions at the time of beta release.
I don't remember a time where we accepted a blocker for something just because it was not as up-to-date as we wanted. It's certainly not in our release criteria. The criteria only care about the quality of the included software. So the correct way would be to find a problem in current GNOME 49 Alpha, and blocking on fixing it (e.g. by providing GNOME 49 Beta). We have no precedence in saying "but we actually wanted a newer version!" (Adam might correct me, with his infinite memory ;-)).
I have to admit that shipping GNOME 49 Alpha in F43 Final sounds like a terrible idea, and I certainly don't want that. But it seems that this is a problem that Workstation WG need to solve, their packages were simply not ready at the right time. If they come to us (I have no idea who naheemsays, the proposer, is, I don't recognize that nick) and say "please use the blocker functionality to prevent a very embarrassing situation", sure, let's talk about it, and ideally also agree on some general approach that give us guardrails for the future, so that the same approach is then not used by every team and package maintainer who decides that a newer package would be better.
For the moment: BetaBlocker -1 BetaFE +1
the correct way would be to find a problem in current GNOME 49 Alpha, and blocking on fixing it (e.g. by providing GNOME 49 Beta)
One such bug seems to be in #1881
BetaBlocker -1 BetaFE +1
Agreed with @kparal
I also agree with @kparal, I don't really see how we can block on something not currently in F43.
With the other details from Kamil I agree.
BetaBlocker 0 BetaFE +1
BetaBlocker -1 AGREED RejectedBetaBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F43 is no longer tracked by BlockerBugs, closing this ticket.