Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2081488 ** Information from BlockerBugs App:
Commented but haven't voted yet: geraldosimiao, mohanboddu
The votes have been last counted at 2022-05-03 23:45 UTC and the last processed comment was #comment-795722
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
I don't see a plausible way to call this not a blocker.
But firefox 100 did only appeared at updates 16h hours ago! And users only started testing a couple of hours now. I didn't know firefox 99 was in such a bad shape...
Sigh. By the book, this has to be a +1. It is indeed important and you can't say that issues in a web browser might not be encountered during live usage.
Sadly...
In the interests of getting a new RC done, and since this is a pretty clear call...
AGREED AcceptedFinalBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.