Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2138870 Information from BlockerBugs App: <img alt="2138870" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2138870" />
Commented but haven't voted yet: kparal
The votes have been last counted at 2022-11-04 20:48 UTC and the last processed comment was #comment-824723
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
While this is "basic functionality" from my POV.
FinalFE +1
FinalFE -1
The feature in question would likely never be used on live images, only after install. This means it can be fully addressed with an update and there is no real benefit to pulling a fix through the freeze, only risk (if the fix somehow breaks something that is important to the live image).
Discussed during a blocker review meeting: https://meetbot.fedoraproject.org/fedora-blocker-review/2022-10-31/f37-blocker-review.2022-10-31-16.00.log.html
The decision was not made yet:
the general feeling here was that folks wanted more information on the nature of the problem and any proposed fix before voting
for the reasons Adam articulated
AGREED RejectedFinalFE
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F37 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.