Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2124145 ** Information from BlockerBugs App:
The votes have been last counted at 2022-09-07 22:57 UTC and the last processed comment was #comment-815833
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 0Day +1
I'm not sure how the blocker tooling handles a 0Day for Beta releases, but let's find out. Since this is a server-side change, there's no need to block approving the RC. (And honestly, for the Beta, I actually don't care if this doesn't get fixed for a day or two after the release).
BetaBlocker -1
Seems this has already been fixed by fedora-infra.
Yeah, this is:
0Day +1
for me. The tooling should be fine with 0Day for Beta - 0Day is an 'acceptance' type, not a 'blocker' type, so far as the highly-advanced bugzilla metadata system is concerned. :P
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F37 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.