-
-
Notifications
You must be signed in to change notification settings - Fork 857
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sorting of releases with multi digit version parts #199
Comments
The sort_natural filter doesn't work, so perhaps we need a |
@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):
This is no longer relevant, because endoflife.date/products/python.md Lines 16 to 27 in 383f384
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 So I really think we should drop this entire endoflife.date/_layouts/product.html Lines 30 to 31 in 383f384
and just |
I like this idea, would clean up the code as well. |
The minor version of Elasticsearch can be double digit, e.g. 7.10 and 7.11. The sorting by releaseCycle is wrong in this case, e.g. 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, 7.11, 7.10.
In #195 I did a workaround with a virtual number in cycleShortHand and sorted by this. I think this could be a problem also in other tools.
The idea is to extend the sorting of such version numbers in
_layouts/post.html
.The text was updated successfully, but these errors were encountered: