Comment 7 for bug 1779859

The "Latest comes first followed up by everything else, version-comparison-ordered, reversed" makes total sense when having 'latest' and all revision numbers, but we have more complex scenarios.

I'm working in adding "the default track first" to the ordering, and found that current behaviour is not what I'd expect when talking about non-version strings.

So, excluding default track (always first, when exists) and 'latest' (always first, except when a DT exists, in that case it goes second), we all agree in the following orderings:

- 3.11
- 3.10
- 3.9

or

- foo
- 3.11
- 3.5

... but what about having several normal ("non version") strings? why it should be reversed?

Example, having foo, bar and baz tracks, shouldn't those "normal strings" be *forward* ordered between them?

- bar
- baz
- foo

In a more comprehensive example:

- 3.12 # current developer-specified default track!
- latest
- bar
- baz
- foo
- 3.11
- 3.10
- 3.9
- 3.8
- 2.17

What do you think?