Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2311907 ** Information from BlockerBugs App:
Commented but haven't voted yet: frantisekz, kparal
The votes have been last counted at 2024-09-16 09:51 UTC and the last processed comment was #comment-932289
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
AGREED RejectedBetaBlocker
Discussed during the 2024-09-12 Go/No-Go meeting [1]:
We can't reproduce it using real crashes, and we have a strong suspicion that the issue would occur only in special code-path for testing the crash reporting feature in Anaconda.
[1] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-09-12/f41-beta-go-no-go.2024-09-12-17.03.log.html
The following votes have been closed:
We might've forgotten about this reason for blocking: "Bug hinders execution of required Beta test plans or dramatically reduces test coverage" https://fedoraproject.org/wiki/Fedora_41_Beta_Release_Criteria#Beta_Blocker_Bugs
I don't think we can release F41 with potentially no testing of crash reporting capabilities (let's say if there are no crashes in Anaconda this cycle). Nominating for Final, at least.
A new ticket was created as #1661 , for some reason.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F41 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.