Sorting of releases with multi digit version parts about endoflife.date HOT 3 CLOSED

@usta @captn3m0 Um, I may be missing something obvious at the moment, but why exactly are we letting the stupid machine reorder our releases (and often screw it up) in the first place?

I see that the sorting was introduced in #42, which references issue #25. And @captn3m0 writes this in the initial issue comment #25 (comment):

It makes sense to sort by release date (in desc order
so newer releases are at the top).

(...)

Since releases are a map currently, it is hard to sort them.

This is no longer relevant, because releases are lists now, not maps. See just about any product page source:

Lists in YAML are guaranteed to preserve order, so the sorting is not needed - if you don't sort it, it will always have exactly the same order in which you specify individual releases.

So I really think we should drop this entire | sort thing here:

and just {% for r in page.releases %}. By doing this, we finally put trust into humans that they know in what order they want releases to be displayed.

from endoflife.date.

The sort_natural filter doesn't work, so perhaps we need a sort_version filter of our own.

from endoflife.date.

I like this idea, would clean up the code as well.

from endoflife.date.