Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2237571 ** Information from BlockerBugs App:
The votes have been last counted at 2023-09-07 22:09 UTC and the last processed comment was #comment-873198
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
We rejected a similar proposed blocker in F38: https://bugzilla.redhat.com/show_bug.cgi?id=2180277 (but we documented it as a common bug)
BetaFE +1 and probably (if it's the same story, no negative effects except the notification): BetaBlocker -1
Yeah, I'm with kparal. BetaFE +1 BetaBlocker -1
I don't think it should block beta but I would consider blocking for GA. BetaFE +1 BetaBlocker -1 FinalBlocker +1
BetaFE +1 BetaBlocker -1
I wanted vote it for a FinalBlocker, regarding this criteria here but then I thought "the criteria stated only for firts boot, and not after other normal use".
AGREED AcceptedBetaFE RejectedBetaBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F39 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.