Re: sbin-merge: what to do?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jul 16, 2024 at 11:13 AM Adam Williamson
<adamwill@xxxxxxxxxxxxxxxxx> wrote:
>
> On Tue, 2024-07-16 at 08:08 +0100, Daniel P. Berrangé wrote:
> > On Mon, Jul 15, 2024 at 05:07:57PM -0700, Kevin Fenzi wrote:
> > > On Mon, Jul 15, 2024 at 08:23:05AM GMT, Zbigniew Jędrzejewski-Szmek wrote:
> > >
> > > > So… the question now: should I pull the plug on the change for F41,
> > > > dump the side tag, and try again for F42? Or wait for some of the patches
> > > > above to be merged? The mass rebuild is supposed to start in two days…
> > >
> > > How hard would it be to move back to the old state?
> > > Does that mean a bunch of reverts and rebuilds? or ?
> >
> > Assuming there was nothing impactful outside of the mentioned side tag,
> > then no rebuilds should be required, just abandon the tag, and do
> > dist-git reverts.
> >
> > > It sounds to me like there's still a lot of outstanding questions, so I
> > > would say moving it to f42 (and trying to land it after branching in
> > > rawhide) would be best, but that depends somewhat on how hard the revert
> > > is... if it's hard it might be better to power on through?
> >
> > Agree it sounds like the wise thing to do is to postpone to F42, to give
> > further time to fully explore the implications. If done right at the
> > start of the F42 dev cycle, there'll be a greater window for finding
> > and resolving any fallout before the F42 beta freeze point.
>
> Yeah, +1 to this. What concerns me about the openQA experience so far
> is the broad range of issues we hit, including ones that were kinda
> 'coincidental' (not actually the thing the test was trying to test).
> Since openQA is nowhere close to comprehensive, this implies more weird
> failures will show up even once it passes all the openQA update tests,
> and we will need time to identify and fix those.

I will note that unless this is done right after F41 is branched from
Rawhide, we won't actually have a lot of time to get it sorted out.
Spring Fedora releases have a lot less time than fall ones because of
all the holidays leading up to it. So this needs to be planned to be
started again *right* after branching completes to maximize time to
fix things.



-- 
真実はいつも一つ!/ Always, there's only one truth!
-- 
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux