On Tue, 2022-11-08 at 07:52 +1100, Bojan Smojver via devel wrote: > Quick question about direct to stable updates in bodhi, such as FF > 106.0.4 and kernel 6.0.7 that are lined up for F37 right now. Such > updates often end up being in nowhere land for quite some time, because > they skip testing to go to stable directly, but the push to stable > cannot happen for whatever reason. > > Would it not be better to get such update to testing in this scenario, > given stable is something that cannot be touched? In other words, > should the algorithm for pushes be changed during such times? Yeah, this is a good point, though I'm not sure how easy it is to fix. I've been leaving those updates in -testing for a while in order to try and be really sure they're OK before we push them stable - we were reserving the option of shipping F37 with earlier version of the kernel, GNOME and Firefox in case the newer versions had problems. But if the updates never make it to -testing, that does restrict the testing they get. I just noticed another consequence of this, too: they don't go into the Silverblue (and Kinoite etc.) testing builds. So if you're running one of those rpm-ostree bases, you can't really get them. I'm on kernel 6.0.6 instead of 6.0.7 for this reason, as that's the most recent kernel build that actually made it to updates-testing. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ 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
