Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2225688 Information from BlockerBugs App: <img alt="2225688" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2225688" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2023-10-30 21:01 UTC and the last processed comment was #comment-881286
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
Not sure I'm seeing the justification here.
FinalFE -1
This is not a crucial application. It can still be fixed in 0-Day updates.
The justification for the FE is that “functionality changed in a way that could break code”, so it's better to push the update to avoid an interface change between Final and subsequent updates. I think this is a good reason, and since this is a leaf application, it should be safe to update it.
FinalFE +1
The presence on the frozen media set might be suboptimal, but it's not critical. Since it's not present on any install medium, it can only be installed via DNF. So long as the maintainer has the update ready to go for 0day, it should be fine.
AGREED AcceptedFinalFE
Discussed during the 2023-10-30 blocker review meeting: [0]
The decision to classify this bug as an "AcceptedFreezeException (Final)" was made on churchyard's justification: avoid the old interface provides being permanently available in the frozen release repo.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-10-30/f39-blocker-review.2023-10-30-16.00.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F39 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.