Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2063969 ** Information from BlockerBugs App:
Commented but haven't voted yet: marcdeop, coremodule
The votes have been last counted at 2022-03-21 18:10 UTC and the last processed comment was #comment-786878
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
That bug refuses to stay dead. FinalBlocker +1
See also #505, #486, probably others.
FinalBlocker +1
Maybe relevant for this topic: https://bugs.kde.org/show_bug.cgi?id=427060 and https://invent.kde.org/plasma/kwin/-/merge_requests/2163
AGREED AcceptedBetaFE AGREED AcceptedFinalBlocker
Discussed during the 2022-03-21 blocker review meeting: [0]
The decision to classify this bug as both an "AcceptedBlocker (Final)" and an "AcceptedFreezeException (Beta)" was made as this is a significant problem in using virtual machines with a release-blocking desktop; we accepted an identical bug as blocker for F35 Final. As it will affect the KDE live we would also like to fix it in Beta if possible.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-03-21/f36-blocker-review.2022-03-21-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.