On Tue, Nov 27, 2018 at 1:40 PM Owen Taylor <otaylor@xxxxxxxxxx> wrote: > > We can definitely talk about whether moving to a slower cadence for > certain parts of the base platform. But people don't judge Fedora on > how beautifully we maintain glibc and gcc - they mostly judge it by > installing it on a laptop and seeing how well it works. And it doesn't > really matter how reliably we can create minimal container images if > the workstation image doesn't compose or doesn't log in. > > We need clear naming for the workstation releases we do. If we want to > call them F30, F30.1, F31, F31.1 we can, but that doesn't inherently > reduce load on releng or remove the need for infrastructure freezes > ... my assumption was that the idea of delaying F31 is to actually > *not* do an operating system release for a year, and that's something > that I don't think we should do on an ongoing basis. Heard, understood, and agreed. Shortening the compose is a root problem to fix if we want to be able to judge reliability of what we want to release. That way we can test it more or less constantly. As for freezes... right now we freeze for a total of roughly 2-3 months out of 12. We can avoid that with a pause -- at least in part, and maybe in total if we finish enough work to minimize freeze coming out of it. That's why taking the break makes sense. Reclaiming that time, year after year, should be a knock-on effect of being able to release more frequently as a non-event. Then there's less (maybe no) reason to freeze -- the worst thing that happens is we pull the lever the next day. So a healthy part of our investment should be in minimizing recovery time. -- Paul _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
