SDL 2.23.1 Released With SDL2 Switching To A New Versioning Scheme

[phoronix]

Phoronix: SDL 2.23.1 Released With SDL2 Switching To A New Versioning Scheme

SDL 2.0.22 was released back in April while now it's to be succeeded by the eventual SDL 2.24 stable and out today is the SDL 2.23.1 pre-release. Besides the shift in the versioning scheme there are many additions coming in this release for this library that's widely used by cross-platform games...

https://www.phoronix.com/scan.php?page=news_item&px=SDL-2.23.1-Released

[-MacNuke-]

This is probably one of the most stupid versioning schemes. If you need to explain similar looking version numbers, you failed...

Instead of just ordering them alphabetically, now I need to parse the text, split the elements, convert to integer and check if it is even...

[Jedibeeftrix]

Is the full wayland support feature that got bumped from 2.22 still scheduled to arrive with 2.24?

[lectrode]

This is probably one of the most stupid versioning schemes. If you need to explain similar looking version numbers, you failed...
Instead of just ordering them alphabetically, now I need to parse the text, split the elements, convert to integer and check if it is even...

Semantic versioning has been around a while and is quite useful when used properly. It conveys to the user the amount of change between one version and another, as well as which ones are backwards compatible, and which ones should be a "safe" update (like point releases).

If you're manually parsing version numbers, there might be an easier way. Coreutils has a sort utility that supports sorting by version number rather easily. Here is an example in BASH that will list the versions in order newest first:

$ echo -e "5.6.1\n5.12.2\n1.53.27"|sort -rV
5.12.2
5.6.1
1.53.27

[FireBurn]

Semantic versioning has been around a while and is quite useful when used properly. It conveys to the user the amount of change between one version and another, as well as which ones are backwards compatible, and which ones should be a "safe" update (like point releases).

If you're manually parsing version numbers, there might be an easier way. Coreutils has a sort utility that supports sorting by version number rather easily. Here is an example in BASH that will list the versions in order newest first:

$ echo -e "5.6.1\n5.12.2\n1.53.27"|sort -rV
5.12.2
5.6.1
1.53.27

You're missing the point, only even minor numbers are considered stable, the odd ones are development

[billyswong]

This is probably one of the most stupid versioning schemes. If you need to explain similar looking version numbers, you failed...

Instead of just ordering them alphabetically, now I need to parse the text, split the elements, convert to integer and check if it is even...

If one use alpha/beta naming instead, "ordering them alphabetically" still won't work. As the order will be like "2.11.x -> 2.12beta1 -> 2.12beta2 ... -> 2.12.0", where "2.12beta1" or "2.12b1" is alphabetically behind "2.12.0".

[skeevy420]

So if they're working on a long-term feature or bug will they just keep adding a 9 to the end until the next even numbered release?

2.24.3999999999

"Why are there so many nines?"

"Variable frame rates on Wayland."

[c117152]

So if they're working on a long-term feature or bug will they just keep adding a 9 to the end until the next even numbered release?

2.24.3999999999

"Why are there so many nines?"

"Variable frame rates on Wayland."

Features aren't worked-on in the even numbered minors. That is, you would have 2.23.1 ... 2.23.2 ... 2.23.N patch-level increments and when the bug is sorted out, they'll back/forward port to 2.22.+1 patch-level.

[lectrode]

You're missing the point, only even minor numbers are considered stable, the odd ones are development

Still no need to parse. Just filter using regex.

Here's an example that only lists the newest version where the 2nd digit (the "minor" version) is even:

$ echo -e "5.13.7\n5.6.1\n5.12.2\n1.53.27"|grep -E "^[0-9]+\.[0-9]*[02468]+\."|sort -rV|head -n1
5.12.2

[FireBurn]

Still no need to parse. Just filter using regex.

Here's an example that only lists the newest version where the 2nd digit (the "minor" version) is even:

$ echo -e "5.13.7\n5.6.1\n5.12.2\n1.53.27"|grep -E "^[0-9]+\.[0-9]*[02468]+\."|sort -rV|head -n1
5.12.2

Ah yes, so simple...