Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2274830 ** Information from BlockerBugs App:
Commented but haven't voted yet: adamwill, kparal
The votes have been last counted at 2024-04-16 15:46 UTC and the last processed comment was #comment-905708
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 agree with Adm on this, it is a blocker as it violates the Change process, and must be reverted for F40.
FinalBlocker +1
please don't vote here, this bug is proposed for FESCo to consider designating it as a blocker. it does not violate any release criteria, really, so cannot be voted as a blocker through the normal process.
Fesco ticket: https://pagure.io/fesco/issue/3196
FESCo decided not to make this a 'blocker' but to request it be fixed with an update to reinstate the service (which to me is exactly what a 0-day blocker is, but ah well.) So, this is:
AGREED RejectedFinalBlocker
The following votes have been closed:
Oh, actually, I missed an earlier agreement line in the FESCo meeting. The two agreements are:
From https://meetbot-raw.fedoraproject.org/teams/fesco/fesco.2024-04-15-19.01.html . So, this is actually:
AGREED Accepted0Day
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.