Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2264944 Information from BlockerBugs App: <img alt="2264944" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2264944" />
The votes have been last counted at 2024-02-26 16:32 UTC and the last processed comment was #comment-897984
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
This isn't really bad enough to be a blocker for me. (Honestly, adding openQA tests for this flow has been on my todo list for years but I never got around to it, now someone actually tried it I am somewhat amazed that it still works at all)...
BetaBlocker -1 BetaFE +1
BetaBlocker -1
The area needs improvements, but I'm not really seeing a blocker here.
I don't see that it is a blocker, but if a fix will exist, it should be included in the release. BetaBlocker -1 BetaFE +1
BetaBlocker -1 BetaFe +1
AGREED RejectedBetaBlocker AGREED AcceptedBetaFE
This doesn't violate Fedora release criteria, but would obviously be a nice thing to have fixed and improved, so rejecting as a blocker and accepting as a freeze exception.
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F40 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.