Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2006393 Information from BlockerBugs App: <img alt="2006393" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2006393" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2022-02-14 19:34 UTC and the last processed comment was #comment-781411
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
Discussed during the 2022-02-07 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug was made as this is an automatic transfer from F35 and we don't know the exact status of F36 currently with this bug. We are delaying a decision to ask cmurf to report back on how F36 is.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-07/f36-blocker-review.2022-02-07-17.00.txt
AGREED RejectedFinalBlocker
Discussed during the 2022-02-14 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Final)" was made as this is still pretty bad if you're affected, but we think the reduction in the time it takes for the situation to resolve is sufficient that it no longer quite qualifies for release blocker status. We'll leave it up to the wisdom of the devs whether it's a better idea to revert the feature if it can't be fixed further.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-14/f36-blocker-review.2022-02-14-17.01.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.