Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2349754 ** Information from BlockerBugs App:
Commented but haven't voted yet: kparal, lbrabec
The votes have been last counted at 2025-03-10 18:17 UTC and the last processed comment was #comment-960208
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
I can't really see a criteria for this but I do believe this is pretty important to have in place.
FinalBlocker +1
Please note that I mainly wanted to start a discussion. If we agree that we want to block on this, we should come up with a new release criterion. I'm interested to hear what people think about this, and possible suggestions on the new criterion wording. Thanks :-)
I agree that there should be a criterion (or criterion and documentation should be adjusted to make it explicit --allowerasing and similar aren't supported), and also feel this should be a blocker since I suspect the absence of --allowerasing will be a cause of consternation for many.
--allowerasing
Discussed during the 2025-03-10 blocker review meeting [1]:
!agreed 2349754 - Punt - People are in general in favor of blocking on this, but there's no direct criterion for it. It seems it will be fixed soon anyway, let's wait a while before potentially proposing a criterion (if we decide to block on it).
[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-03-10/f42-blocker-review.2025-03-10-16.01.log.html
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F42 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.