Comment 4 for bug 1779859

The current ordering seems to be (but is not documented to be, afaik) alphabetical, except that latest comes first. This obviously breaks down for projects that want to use version numbers for tracks, such as go, or even etcd itself as soon as it reaches two-digit version numbers.

Version sort would cover those, but not cover projects that want to use some other descriptor (for example, chrome might use stable/beta/dev/canary).

We could look at everything that has tracks today and see how they want them sorted, and use those numbers to inform the decision. I'm not sure that's wise at we're not yet where we want to be in terms of adoption, though.

In any case it's a sufficiently broadly-impacting issue and feature that I think it needs wider (and higher) commentary.