Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=1816547 ** Information from BlockerBugs App:
Commented but haven't voted yet: coremodule, kleinkravis
The votes have been last counted at 2021-01-19 13:12 UTC and the last processed comment was #comment-710459
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
FinalBlocker +1
If it was a blocker in F32, I don't see a reason for it to not be a blocker in F33.
I can confirm the problem. FinalBlocker +1
AGREED AcceptedFinalBlocker
Discussed during the 2020-09-14 blocker review meeting: [0]
The decision to classify this bug as an "AcceptedBlocker (Final)" was made as it violates the following criterion:
"All critical path actions on release-blocking desktops must correctly display all sufficiently complete translations available for use" (with precedent from a similar bug in F32)
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-09-14/f33-blocker-review.2020-09-14-16.01.txt
The following votes have been closed:
FinalBlocker +1 This is very important, we can't scare off international users
Release F33 is no longer tracked by BlockerBugs, closing this ticket.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.