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 would suggest that we use a more explicit name
strictmode instead of
Before voting, I have a couple of questions:
Would the versions on
strictmode track and default track be mutually-incompatible, besides confinement settings? Meaning, if I was running default track and try to install
strictmode, would that just work, or do I need to migrate my data/configuration, or would things break horribly?
If the new track would be experimental and abandoned at some point, people trying it would become stranded and not get any updates (without explicit actions). Would a
strictmode branch which does expire and move people to the parent channel would be a better fit? If you plan to work actively on this, releasing stuff to the branch every 30 days so the branch doesn’t close automatically could be feasible.