Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=1829079 ** Information from BlockerBugs App:
Commented but haven't voted yet: kparal, kleinkravis
The votes have been last counted at 2021-01-19 13:12 UTC and the last processed comment was #comment-710461
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
AGREED AcceptedFinalBlocker See bug for more info
The following votes have been closed:
Has this been reported upstream?
This is a place to discuss the blocker status, nothing else. You want to ask in the bugzilla report itself.
Until I can verify that this has been reported FinalBlocker +1
It has been fixed upstream. https://gitlab.gnome.org/GNOME/gdm/-/issues/600 FinalBlocker -1
@kleinkravis Hey, this project's readme contains a number of links at the top which talk about the blocker process and how it works: https://pagure.io/fedora-qa/blocker-review In particular, we vote on the blocker status based on our release criteria. Whether the bug was or wasn't fixed upstream isn't relevant (and it surely doesn't make any sense to reject a blocker because a fix is already available upstream). Please read those documents and ask any questions in the test mailing list. Thank you.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F33 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.