V Mon, Feb 08, 2021 at 10:23:17AM -0500, Matthew Miller napsal(a): > On Mon, Feb 08, 2021 at 04:09:19PM +0100, Martin Curlej wrote: > > It would be great if we could start a discussion about how modular > > obsoletes will be used in Fedora? Where will be they stored? Who will be > > able to change them? Just a couple of questions to get the discussion > > started. Any involvement of the Fedora community is highly appreciated. > > On EOL, not specifically Obsoletes, but since they're deeply related: > > In general, the idea is that in Fedora context, modules are most useful when > they're longer-lived than the normal 13-month release cycle (rather than the > RHEL case of being shorter than 10 years). I suggest therefore: > > 1. Module EOL should always align with a Fedora Linux release EOL (i.e. > May/November every year). That way, people aren't ending up with modules > randomly ending at unpredictable times. > > 2. If an upstream is ending at an unaligned time, Module owners should plan > to separately deal with any critical security issues for another couple > of months, or EOL the module at the _sooner_ date. > > 3. If an upstream is something that changes faster than the Fedora Linux > release cycle (shorter than 13 months), the module stream should be > rolling rather than pinned to those short-lived versions. > I don't agree. Aligning EOLs to Fedora release proofed not working for me: When creating a stream, you are not allowed to select May/Novemeber. You can only select June/December. Fedora releases do not align to May/November. E.g. F33 G.A. was 2020-10-20, F31 EOL was 2020-11-24. What does November mean? 2020-11-01? 2020-11-30? How do you want to prepare a new Fedora release with respect to the streams EOLing with that Fedora release? Do you want to keep the to-be-EOLed streams in the compose of Beta? G.A.? See what happend with perl:5.28 in F33 <https://pagure.io/releng/issue/9736> -- relengs EOLed it before Beta in September. In my opinion binding module EOLs to Fedora EOLs is not doable and they should be kept free. If you wanted to implememt the aligned EOL, you would have to wait on a new Fedora release (because the exact day of EOL is not knows until a release is made), include the to-be-EOLed streams in the new release, then set the EOL, and publish it through updates. A user experience would be: At G.A. -- I have a new F33 with perl:5.28. A week after -- perl:5.28 EOLs in 4 weeks. If you wanted to prevent from this experience, relengs would have to clean up Beta and G.A. composes from the to-be-EOLed streams. -- Petr
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
