Hi, we’d like to request a new track called “20” to publish system snaps that will use core20 as base, which are:
bluez network-manager modem-manager
We plan to follow the same convention as gadget/kernel snaps that have the base as track, like
pc-kernel. This changes the convention that we were previously following, which was based on upstream version. The reasons are:
- These snaps are closely tied to a given UC release. These are system daemons that control parts of the system that need to be in sync with the core snap. For instance, DNS management changed between UC16 and UC18, and NM takes control of this when installed in the system.
- Now these snaps use the equivalent debian package sources for building: we plan to track Ubuntu releases, not upstream versions. As occasionally the upstream version of a package for a given Ubuntu series can be upgraded, it is better to base the track on the series instead of in a concrete version. See this publishing history as an example of an occurrence of this kind (for Bionic).
- Due to the previous reasons, it is more intuitive for users to see the UC release as a track, so for a given UC they have a hint of the track to follow. Versions do not expose that information immediately.