Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2063381 Information from BlockerBugs App: <img alt="2063381" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2063381" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2022-03-14 18:55 UTC and the last processed comment was #comment-785751
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
GNOME Shell crashes are sad, because they inevitably result in data loss. But unless it occurs especially frequently, it seems like a stretch to consider this a failure of the default panel functionality criterion.
Ah, I meant:
FinalBlocker -1
I don't like it, but it hasn't crashed for me yet here.
AGREED AcceptedFinalBlocker AGREED AcceptedBetaFE
Discussed during the 2022-03-14 blocker review meeting: [0]
The decision to classify this bug as both an "AcceptedBlocker (Final)" and an "AcceptedFreezeException (Beta)" was made as it's happened enough times to enough people to consider it a conditional violation of several criteria (e.g. the panel criterion) for now. We will backport the proposed fixes and do further testing to clarify the situation.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-03-14/f36-blocker-review.2022-03-14-16.01.txt
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.