Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1937308 Information from BlockerBugs App: <img alt="1937308" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/1937308" />
Commented but haven't voted yet: jbwillia, coremodule
The votes have been last counted at 2021-03-15 20:59 UTC and the last processed comment was #comment-721304
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
In the event that we end up blocking for other reasons, getting a fix for this would be highly desirable. However, given the easy workaround and the fact that this is a Beta release, it would fail the "last blocker at Go/No-Go" test.
BetaFE +1
That's easy. For the hard one, I think I'm
But also +1 to waiving it under the late blocker exception.
I'm at least: BetaFE +1 thinking about blocker for now, but let's get it accepted as an FE. AGREED AcceptedBetaFE
The following votes have been closed:
I agree - this fails the "last blocker" test
BetaBlocker +1 BetaFE +1
I think this is a blocker, but I would also waive it with the late blocker exception (and that this is Beta, not final)
+BetaFE+1
Discussed during the 2021-03-15 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug was made as this isn't a completely clear call for Final blocker, so since it's confirmed fixed in Beta anyway we're just going to duck it by waiting for that fix to be pushed stable.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-03-15/f34-blocker-review.2021-03-15-16.00.txt
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F34 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.