On Thu, Sep 20, 2018 at 9:12 AM Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > > On Tue, Sep 18, 2018 at 10:48:46AM +0200, Adam Samalik wrote: > > There is another concept in Modularity we can use here: defaults. You could > > have both streams 1.7 and 1.8 built for all active (non-EOL) Fedora > > releases, but have different default for each. So in your case, F27 could > > have 1.7 as a default and F28+ could have 1.8 as a default. > > > > Independently of this, you could also retire 1.7 with the end of F27 if > > there was no need to have it in the future releases. > > Is there a way for users to say "keep me on whatever module is the default" > when upgrading? That would be a violation of the design principle that users should never have their module stream change underneath them without their consent. Now, it gets a little trickier when we talk about upgrades from a release that supports 1.7 to one that no longer does... in that case I believe our expected behavior is that the user is expected to switch to the newer stream *before* initiating the upgrade process. So they'd do: ``` dnf module enable foomodule:1.8 dnf distro-sync dnf system-upgrade --releasever=nextversion download ``` _______________________________________________ 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
