On Mon, Apr 06, 2020 at 03:02:02PM +0000, Zbigniew Jędrzejewski-Szmek wrote: > On Tue, Mar 31, 2020 at 12:13:16PM +0200, Daniel Mach wrote: > > >> # A string representing a Name of a module that is EOLed > > >> # MANDATORY > > >> module: nodejs > > >> > > >> # A string representing a Stream of a module that is EOLed > > >> # MANDATORY > > >> stream: 11 > > >> > > >> # A string representing a Context of a module that is EOLed > > >> # If not specified, all contexts get EOLed. > > >> # NOTE: consider specifying a list of contexts > > >> # OPTIONAL > > >> context: aabbccddee > > >> > > >> # A string representing UTC date in ISO 8601 format: YYYY-MM-DD[T ]HH:MMZ > > >> # It is strongly recommended to keep HH:MM to 00:00. > > >> # If not specified, the module is EOLed immediately. > > >> OPTIONAL > > >> eol_date: 2020-03-19T00:00Z > > > > > >Normally we want the obsoletes to happen when doing a 'dnf system-upgrade' > > >operation, and not based on time. Does this allow us to tell dnf for this > > >happen during an upgrade, but not before? > > There are scenarios when you don't run system-upgrade and you still > > want the obsoletes. Consider Rawhide. We'll need a way how to > > trigger modular obsoletes even during normal upgrade/distro-sync > > transactions. > > > > Setting eol_date to the future allows informing a user about > > upcoming obsoleting event so they can eventually migrate manually. > > For some context (RHEL...) time-based obsoletes make plenty of sense. > But in Fedora we established a policy that obsoletion and other > significant stream changes happen at "release boundary", which for > each user is whenever they choose to upgrade, so not time-based. > That's a great motivation, but this is not how it works in the real world. A packager asks for a branch and sets an end-of-life date. The date is enforced to align with a Fedora cadence. I.e. 4th and 10th month of a year. The packager builds a module from that branch for _all_ Fedoras and pushes the builds to the stable repositories. Once the end-of-life day comes, the packager stops maintaining the stream. That day there is exactly one Fedora release that also reached the end of life. But all the newer Fedora releases are still supported, but the stream there is not. You have an unsupported stream in a supported Fedora release. That's the outcome of decoupling a stream life cycle from a Fedora life cycle. -- 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
