Create new track for "cluemaster-mediadisplay-core"

Hello. I’m requesting a new track to be added called “DEV”. I would like a separate track for us to use solely for our development builds which point to an entirely different set of servers for us. It gets confusing sometimes when our builds are mixed in the default track if we forget to change the yaml snap version names.

Hi there!

Per Process for aliases, auto-connections and tracks 2, we need a 1-week voting/discussion period, so I’ll check back on the discussion and votes in a few days.

I have three questions before casting my vote. The following questions also apply to the other two snaps that you are requesting a DEV track for, cluemaster-videoplayer-core and cluemaster-roomcontroller-core.

  1. What are the snap’s release cadence? How often is a new major version (potentially requiring a new track) released? Is this documented somewhere by upstream?
  2. Is there some commitment from upstream on maintenance of old versions? Will older versions be supported when newer versions are created?
  3. Are new versions backwards-incompatible? meaning, if I was running non-DEV and try to install DEV, will that just work, or do I need to migrate my data/configuration, or will things break horribly?

Thanks!