On Tue, Jul 12, 2022 at 2:46 PM Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote: > > On Mon, 2022-07-11 at 07:02 -0400, Josh Boyer wrote: > > On Sun, Jul 10, 2022 at 12:34 PM Miroslav Suchý <msuchy@xxxxxxxxxx> wrote: > > > > > > Dne 08. 07. 22 v 4:59 Stewart Smith via devel napsal(a): > > > > > > Another - what do we do about, e.g., Fedora IoT and Fedora CoreOS, > > > which have their own somewhat different release/life cycles? What about > > > module lifecycles? What is it about *lifecycles* that's important, > > > anyway? Don't we maybe want to just have a sort of generic system for > > > "important events"? > > > > > > I view it as a mechanism to communicate well in advance of when someone > > > is going to have to do work. > > > > > > Fedora is the simple case: every 6-12 months you're going to have to > > > upgrade the version of the OS. > > > > > > And when implementing this for Fedora, can you bear RHEL in mind too? Because it has several levels of EOL > > > > > > https://endoflife.software/operating-systems/linux/red-hat-enterprise-linux-rhel > > > > RHEL is already implementing it's own scheme for lifecycle metadata. > > How does it work, and is it F/OSS? Is it integrated with the actual > release processes or just updated manually? It's a work in progress and will likely be tied to the Insights service that comes with a RHEL subscription. josh _______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
