Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1870476 Information from BlockerBugs App: <img alt="1870476" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/1870476" />
The votes have been last counted at 2021-01-19 13:13 UTC and the last processed comment was #comment-710472
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
BetaBlocker -1 BetaFE +1
I'm not seeing any criterion we could apply for FinalBlocker decision.
that's -4/+4, will update bug.
For bookkeeping, it's good to use AGREED. That will print a record of the current state as a comment, which means even if somebody edited their comment retroactively, it would still be clear what was the exact state at that time.
AGREED RejectedBetaBlocker AcceptedBetaFE
The following votes have been closed:
Now that we have a new criterion specifically for this: https://fedoraproject.org/wiki/Fedora_33_Final_Release_Criteria#First_boot_experience I believe this meets the requirements of a FinalBlocker: FinalBlocker +1
FinalBlocker +1
FinalBlocker +1 This may discourage new users from using online account functionality.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F33 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.