The following scenario is not elaborated in the documentation and actually was discussed in another thread. I just wanna double-check how does store behave in such a case today.
I requested 17.06 track for docker-snap, and that track holds docker 17.06.0 Quarterly release and subsequent bug fixing versions(17.06.1, 17.06.2…etc).
3 months later, when 17.09 quarterly release is out, another requested track 17.09 is opened up for docker-snap and we use it for 17.09 snap package publishing.
Then how can end-users upgrade docker snap to 17.09 if 17.06 is installed previously?
What’s the store’s behavior if we explicitly close 17.06 track by running ‘snapcraft close 17.06’? Do people stay at 17.06 track forever or store internally fallback to next track here? If it’s the former case, does that mean people have to upgrade to latest track(17.09) manually?