Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2346634 ** Information from BlockerBugs App:
Commented but haven't voted yet: dcavalca
The votes have been last counted at 2025-02-24 16:36 UTC and the last processed comment was #comment-957617
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
What's the justification for this being a freeze exception? The bug says "it includes a number of bugfixes and additional features that will be useful to have in the stable release" - sure, but why do we need to get it in during Beta freeze specifically?
9.6.4 includes a bunch of subpackages that enable extra "optional" features that are more or less tablestakes in real deployments. It'd be useful to have it in the Beta so I can test against a f42 container to make sure it works properly to build docs for the two projects I have that use mkdocs (CentOS and Asahi Linux), as I'd like for f42 to work out of the box for this.
well, we do container builds and publish them nightly anyway...but if you just mean you don't want to wait out the freeze, ehh, i guess it'd be ok...
Yeah, my plan was to start using the f42 containers upstream asap, so we could get anything that potentially needed fixing sorted out long before final.
OK, sure. BetaFE +1 AGREED AcceptedBetaFE
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.