Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2011774 ** Information from BlockerBugs App:
Commented but haven't voted yet: kparal, coremodule
The votes have been last counted at 2021-10-11 19:07 UTC and the last processed comment was #comment-757288
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
This is borderline usable (the repos are adjusted correctly, just jump around unexpectedly, and the other repos can get redrawn back into a proper state with page changes), but it's such a horrible experience, that I'm hesitant to call this as satisfying basic functionality. I'm leaning more towards FinalBlocker +1, but I'll wait for more opinions first.
FinalBlocker +1
AGREED RejectedFinalBlocker AGREED AcceptedFinalFE
Discussed during the 2021-10-11 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Final)" and an "AcceptedFreezeException (Final)" was made as we agreed that while this looks bad, the operation does work, so critical functionality is maintained. It's accepted as an FE issue if it can be fixed relatively safely, as it does look pretty bad.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-10-11/f35-blocker-review.2021-10-11-16.00.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F35 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.