I’m trying to work out how best to achieve what I need with the snap versioning & release system. I feel like this is a scenario that many software maintainers are likely to hit (and so may already be covered somewhere).
I’ve been releasing documentation-builder using the channels, without worrying about tracks so far. So currently,
latest/stable carries revision
latest being the default track).
I’d like to release version
2.0.0, which will include a significant breaking change for the user - now the user will have to provide a template, where previously the template was included. This will be the official new version of
documentation-builder, and I won’t be actively maintaining
1.x any more.
I don’t think it’s a good idea to automatically upgrade any users to
2.0.0, it should only be something they do deliberately, as they now need to actively provide a template. I’d also like to reserve the option to automatically push e.g.
1.6.1 to those with
1.6.0 at some point if needed.
I could open a new track, e.g. the
2.x track or something, but the problem with that is that the
latest track would continue to exist just for
1.x versions, and would be quite misleading.
Is there any way to leave existing users on a
1.x track, but reclaim the
latest track for my new
2.x set of releases?