Hi there,
archetic has no existing tracks, so per Process for aliases, auto-connections and tracks , we need a voting/discussion period, so I’ll check back on the discussion and votes in a few days.
Thanks for the detailed information, I think this is a reasonable use for tracks and I’m +1 on creating the testnet and mainnet tracks.
You could use latest to host your mainnet builds, but if you prefer to have the two named tracks and designate one of them as default, it’s entirely possible to do so.
Once the tracks are created, you can manage your default track yourself in snapcraft.io (go to your snap’s page, then to the releases tab).
One thing to note is that the latest track cannot be removed or renamed; if someone specifies --channel=latest/stable explicitly, for example, it will still be valid. What you can do here is simply close the latest track with snapcraft close - or just never release anything to it.
- Daniel