Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2264794 Information from BlockerBugs App: <img alt="2264794" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2264794" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2024-02-26 16:45 UTC and the last processed comment was #comment-897989
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
Discussed during the 2024-02-19 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug was made as the report does not explain which images or hardware platforms are affected by this, which seems like required information to make a blocker decision.
[0] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-02-19/f40-blocker-review.2024-02-19-17.00.log.txt
As this only seems to affect one specific device which is not on the current 'supported platforms' list (either of them):
BetaBlocker -1
Also as it sounds kinda complicated and is of marginal benefit:
BetaFE -1
I have a suspicion the need to support this case will only grow in the future, but for now it seems pretty explicitly not supported.
BetaBlocker -1 BetaFE -1
AGREED RejectedBetaBlocker AGREED RejectedBetaFE
The scope of Hardware this issue affects doesn't apply to any of the "blocking" hardware (at this point, it seems it is just one device). The fix kinda complicated and is of marginal benefit, so rejecting both as blocker and freeze exception. If there is a fix developed during the beta phase, it can be pushed after the beta release and before the final freeze starts.
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.