On Thu, 2025-09-11 at 02:48 +0200, Neal Gompa wrote:
> On Thu, Sep 11, 2025 at 2:25 AM Gary Buhrmaster
> <[email protected]> wrote:
> > 
> > On Wed, Sep 10, 2025 at 9:01 PM Neal Gompa <[email protected]> wrote:
> > > 
> > > I think the expectation was for dracut 108 and systemd 258 to be used in 
> > > tandem.
> > 
> > The changes for dracut 108 are significant, and
> > clearly could break something in F43, but I think
> > getting it into F43 would be for the best rather
> > than waiting for F44.  Would this need to be a
> > late F43 FESCo change exception, or could it
> > be a beta freeze exception?  I don't really like
> > either choice, but this would seem to be the
> > time to make a decision.
> 
> Submitting it as an update to F43 and having a freeze exception filed
> would be sufficient.

Well, yes, but we'd need justification to accept it as an FE. "We kinda
feel like these things are meant to go together!" isn't really
sufficient justification. Is there some actual, concrete problem
someone can point to with the current stable packages in F43 - systemd-
258~rc4-1.fc43 and dracut-107-6.fc43 ?

Once Beta is done, there is no technical restriction preventing you
landing this before the Final freeze, but the policy is
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#beta-to-final-freeze
, "The branched tree should now be stabilized and prepared for release.
Major changes should be avoided during this period."
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @[email protected]
https://www.happyassassin.net



-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to