"0.9.x" track for Makhber snap

store-requests
2

Hi,

The makhber snap has no existing tracks, so per the Process for aliases, auto-connections and tracks , we need a 1-week voting/discussion period, so I’ll check back on the discussion and votes in a few days.

I have a few questions/comments before casting my vote.

  1. Can you explain why this track name is required for makhber? Is there any particular reason why its name cannot simply be 0.9?

  2. In general, we don’t recommend using tracks to segment minor or patch versions. Trying to use tracks to designate minor or patch versions negates many of the advantages of using a snap in the first place. Having said that, I wanted to ask whether new versions are backwards-incompatible. Meaning, if I was running 0.9.x and try to install 0.10.x, will that just work, or do I need to migrate my data/configuration, or will things break horribly? Lastly, what is the expectation when e.g. version 1.0 comes out? Will that be cleanly upgradeable from e.g. 0.9 installations or will it imply breaking changes?

  3. What’s makhber’s release cadence, how often is a new major version (potentially requiring a new track) released? is this documented somewhere by upstream?

  4. Is there some commitment from upstream on maintenance of old versions?

Thanks,

Odysseus