Hi,
Please create a new track legacy for the rundfunk snap:
We use latest/stable for the current core20 line.
legacy/stable will be a maintenance-only compatibility line for users
who cannot migrate immediately.
Thanks.
Hi!
Would it make sense to have a track name with a specific version instead of a relative name like legacy. You might in the future, for example, have another set of maintenance-only users, which would require a different name like legacy2.
It might also make sense to transition to track names with specific version numbers. If your new major version is v2.x.x, then you can use 2 instead of latest and 1 for the ‘legacy’ v1.x.x users. In the future if 2 becomes ‘legacy’ as well, then nothing has to be done for these users as they can simply remain on track 2.
In any way, these are just some ideas that might be useful in your case. If they don’t apply, please let me know and I will create the legacy track as requested.
1 Like
Hi,
thanks for the suggestion.
In our case legacy is not an older major release line, it’s a compatibility line. We plan to keep a core18 based build (incl. i386) for users who can’t move to core20 yet. While keeping the mainline on the existing latest/stable track to avoid forcing existing users to switch tracks.
We don’t expect multiple separate maintenance only groups, so a single legacy track should be sufficient. If this ever changes, we can revisit and move to a versioned track scheme.
If that works for you, please proceed creating the legacy track. Thanks!
Hey, I just created the legacy track.
Thanks!
Moaaz Assali