Request 3 tracks for snap "mtk-neuropilot"

store-requests
2

Hello,

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 four questions before casting my vote.

  1. What’s mtk-neuropilot’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?
  3. Are new versions backwards-incompatible? Meaning, if I was running g1200 and try to install g700, will that just work, or do I need to migrate my data/configuration, or will things break horribly?
  4. Is there a possibility of introducing a new set of changes for a specific hardware board, that could potentially require a new track only for that board? E.g. Say I’m using g1200 and a new version of mtk-neuropilot is released that’s backward-incompatible with the existing version for g1200. New tracks for g1200 (e.g. g1200-a) would then need to be created, for every such case, no?

Thanks,

Odysseus