On Sat, Dec 18, 2021 at 3:35 AM Alejandro Saez Morollon asm@redhat.com wrote:
On Tue, Dec 14, 2021 at 5:01 AM Matthew Miller mattdm@fedoraproject.org wrote:
On Mon, Dec 13, 2021 at 02:22:24PM +0100, Alejandro Saez Morollon wrote:
A hypothetical new release cycle would look like this:
- Fedora N release follows Go upstream as close as we can.
- Fedora N-1 sticks with the latest major version of Go that was
available on it until the release of Fedora N.
Another hypothetical approach could be using modules with each upstream supported release in a stream.
This seems like the thing Modularity was invented to do, and would have the advantage of being able to be consistent across a release with a "baseline" version but also provide options.
But AFAIK, only users can select a module stream, right? I mean, packages can't be build on top of a module stream so new needs of package maintainers cannot be satisfy with modules.
I'm curious about how other SIGs deal with these scenarios...
I can't think of anyone I know personally who actually uses "modularity" since its introduction, As Zathros said in the old Babylon Five episode "this is wrong tool!"