Hi store team,
I’d like to request a track creation grant for the nanomq snap
(publisher: giaever-online), so that major-version tracks can be
created self-served as upstream majors arrive.
Snap: nanomq (Install nanomq on Linux | Snap Store)
Publisher: giaever-online (Giaever.online)
Packaging: GitHub - giaever-online-iot/nanomq: All-around Edge Messaging Platform · GitHub
Upstream: GitHub - nanomq/nanomq: An ultra-lightweight and blazing-fast Messaging Bus/MQTT Broker for Edge & SDV · GitHub
Requested track naming pattern: MAJOR — one track per upstream
major version: 0 (current 0.x line), then 1, 2, … as upstream
releases them.
Cadence: low — a new track only when upstream ships a new major. Within a major, minor and patch releases are backwards compatible for broker deployments, so they flow as updates on the same track.
Rationale: NanoMQ is an MQTT broker — infrastructure that connected services and devices depend on. Deployments (particularly unattended Ubuntu Core / IoT installs, which this snap targets across amd64, arm64, armhf, ppc64el, s390x and riscv6) need to stay on a major version and receive compatible updates automatically, while adopting a new major — where breaking protocol/config changes are allowed — deliberately. Tracks are the store’s mechanism for exactly this.
Precedent: same publisher and track lifecycle as my
home-assistant-snap (granted tracks 2025.7 … 2025.11), and a
parallel TCG request for the home-assistant snap.
Commitment: tracks will only be created following the MAJOR
pattern above, one per upstream major release; no other track names
will be created under this grant.
Thanks!