Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2358501 ** Information from BlockerBugs App:
The votes have been last counted at 2025-04-09 08:46 UTC and the last processed comment was #comment-964909
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
FinalBlocker +1 FinalFE +1
I think the most-relevant criterion is this one:
for any deployment of that Edition in accordance with the rest of these criteria, the relevant fields in /etc/os-release must include the correct Edition name
https://fedoraproject.org/wiki/Fedora_42_Final_Release_Criteria#Self-identification
It doesn't clearly say that it needs to have the "Edition" identifier. And there's a question whether the full edition name also includes the edition suffix. I would say that 90% of the intention of the criterion is satisfied, you can clearly identify the installation as either Workstation, KDE, etc. So it's not a clear-cut blocker in my eyes (quite opposite, I'd lean a bit to -1 blocker, actually).
Currently: FinalBlocker 0 FinalFE +1
If we take this as a blocker, we must fix CoreOS identification as well, it has the same issue.
Personally I'm:
FinalBlocker +1
under that criterion. The CoreOS case is tricky because I think we might consider the 'canonical name' of the CoreOS edition to be just "Fedora CoreOS", not "Fedora CoreOS Edition"...it all gets a bit fuzzy there, though. we might need council to think about this.
AGREED AcceptedFinalBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F42 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.