Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2061528 Information from BlockerBugs App: <img alt="2061528" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2061528" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2022-03-07 22:44 UTC and the last processed comment was #comment-784841
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 RejectedFinalBlocker AGREED AcceptedBetaFE
Discussed during the 2022-03-07 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Final)" and an "AcceptedFreezeException (Beta)" was made as this seems to have no practical consequences and works on every boot after the first, so we decided it's not a sufficient violation of the criterion to block the release on. However it is confounding to see on first boot, so we grant an FE to fix that for Beta if possible.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-03-07/f36-blocker-review.2022-03-07-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.