Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2308952 ** Information from BlockerBugs App:
Commented but haven't voted yet: sgallagh, frantisekz
The votes have been last counted at 2024-09-03 18:35 UTC and the last processed comment was #comment-929676
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
Looking at the criteria, we don't actually require this, and it could be fixed with a (stable) update to fedora-repos. But I'm happy to say at least:
BetaFE +1 AGREED AcceptedBetaFE
The following votes have been closed:
Yeah, there is no official criterion for this, but I think there should be. For now, I'm going to say:
BetaFE +1
and propose that FESCo declare it a blocker. (EDIT: at least a 0day blocker)
Retracting my vote given the above (no criterion present). BetaBlocker 0
I opened https://pagure.io/fesco/issue/3266 to get FESCo blocker approval.
I also feel that this should be a full blocker, not a 0day, since that would introduce a confusing delay (u-t would be enabled AFTER the first update of the system, which could cause user confusion and complaint).
In absence of a criterion, I can't vote for it to be a blocker. I can see the argument for a criteria being written.
BetaBlocker 0
I don't think it's terrible enough to need FESCo to declare it a blocker, tbh, just enabling it with an update after Beta ships seems like it would be not that bad to me. I think that's why we wrote the criteria that way.
But anyway, since the fix is trivial I didn't bother making much of a fuss because we will certainly fix it as an FE.
I wouldn't expect it to be a criteria but it is a miss in the branch/freeze process which was missed.
Discussed during the 2024-09-03 blocker review meeting [1]:
As this is already accepted as an FE and the blocker status appears to be subject to FESCo jumping all over it, we'll delay the decision on blocker status while that happens. in any case the bug will shortly be fixed.
[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-09-03/f41-blocker-review.2024-09-03-16.00.log.html
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.