Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2222649 ** Information from BlockerBugs App:
Commented but haven't voted yet: tflink, frantisekz
The votes have been last counted at 2023-08-28 13:40 UTC and the last processed comment was #comment-871161
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
BetaFE +1
I'm confused as to why this is a FE. Is it part of any of the images? If not, people will have updates-testing enabled post-install and can install it as usual.
Ohh ok. Yes, I don't think it is part of the workstation or the kde spin isos. You have a good point.
Trying to find help on the docs https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process#Freeze_exception_bug_principles
I agree, I'm not sure what a FE accomplishes here. Generally I like as many (limited disruption) changes incorporated in the beta image as possible, but as mentioned above, I don't think this would hit any images.
BetaFE 0
I'm thinking here about something: If someone have this package installed on his F38, and try to do a distro upgrade to F39, the upgrade will not be accomplished because the package with the fix on F39 is on testing repo only... Is that right? This behaviour grant a FE status or not? Its just a thought, I'm not really sure.
I'll change my vote for now:
Good point, I had not considered the upgrade case.
Yes, @geraldosimiao is correct. We typically accept FTI bugs as FEs because it helps people upgrade during freezes, this is a longstanding convention. I've added this case to https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process#Freeze_exception_bug_principles .
Alright, this makes things clear.
And not only because of upgrades but also because of the base repo state. That doesn't apply for beta, but should a package be FTI into the GA, it'll stay FTI in the fedora baserepo forever for that release (which is not nice, creates confusion from time to time when doing some work with packages, ...).
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F39 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.