The original request in this bug is "There should be a well-defined order for tracks.".
They are ordered alphabetically save for "latest" which always appears first. Alphabetical ordering may not make the most sense for numeric track names, but it *is* a well-defined order. That said, if something that handles numeric names more nicely (as we've seen Debian ordering does) is preferred, we can look into it.
An interesting case is:
curl -H "Snap-Device- Series: 16" https:/ /api.snapcraft. io/v2/snaps/ info/etcd? fields= channel- maps-list, name,snap- id | jq '."channel- map"[]. channel. track' | uniq
"latest"
"2.3"
"3.0"
"3.1"
"3.2"
"ingest"
The original request in this bug is "There should be a well-defined order for tracks.".
They are ordered alphabetically save for "latest" which always appears first. Alphabetical ordering may not make the most sense for numeric track names, but it *is* a well-defined order. That said, if something that handles numeric names more nicely (as we've seen Debian ordering does) is preferred, we can look into it.