On Thu, Sep 20, 2018 at 09:35:41AM -0400, Stephen Gallagher wrote:
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.
That's fine and all, but I don't want to violate a different principle: release-to-release updates on Fedora should be painless. Modularity is supposed to make that better. The no-switch-without-consent design principle is fine, but in order for these two things to both be true, we need a better UX than erroring out and hoping the user knows what to do.
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
How do they know they need to do the former?
If it's "they'll find out when dnf system-upgrade errors out!", then see above. I'm ... not enthused. Something in dnf system-upgrade needs to do it; possibly a "dnf system-upgrade prep" step before "download".
Also, since we're enabling modules on Workstation, what happens in GNOME Software?