Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2135772 ** Information from BlockerBugs App:
The votes have been last counted at 2022-10-18 21:41 UTC and the last processed comment was #comment-821946
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
While yet another Calendar blocker will certainly not be popular, I think this is a blocker-worthy problem. Weekly events are very common, and the Calendar not just freezes, it will also make it impossible to get rid of that event (can't delete it, edit it, nothing).
FinalBlocker +1
FinalBlocker -1 FinalFE +1
This is a "late blocker", there is no clear sign that a fix is imminent and, barring evidence to the contrary, it is likely to be fixable with an update.
@sgallagh has a good point
Well, for me, it's a clear blocker:
FInalBlocker +1
but it's a candidate for waiving. The rules about blockers being late relate to waiving them, not rejecting them. The procedure is to accept it and then debate waiving it.
AGREED AcceptedFinalBlocker
We can discuss waiving at the go/no-go; this at least lets us include a fix if one shows up and we decide to respin.
The following votes have been closed:
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.