Well that explains why I’m on version
0.0.7899999999998765
7899999999998765
Even if a developer would make a commit every second, it would take 250 million years to reach version 0.0.7899999999998765
Most of the mistakes they have to fix are incorrect version numbering.
I have seen people just add '9’s to it, so to not upgrade the minor, so 2.6.997 gets 2.6.9997 and so on
Some people cannot math.
no it’s more like
Copy of New File (2)_finalThey go up to version 0.0.8, 0.0.9, then they go to 0.0.91, 0.0.92, … 0.0.99, 0.0.991, …
And here I was holding my breath for the legendary 0.0.7899999999998766. Thanks for ruining all my dreams.
AI slop bbyyyyyyy!!!
Weak humans would use 250 million years, strong AI can slop it in 1 year.
/S
It’s more logical than Linux’s version numbering system:
Does the major version number (4.x vs 5.x) mean anything?
No. The major version number is incremented when the number after the dot starts looking “too big.” There is literally no other reason.
And «too big» for Linus is around 20.
See that’s totally logical, but it makes more human sense than computer sense.
It’s logical if Linus has some numbers autism
Shame-antic versioning
Under semantic versioning, you should really be ashamed of bumping the major number, since this means you went and broke backwards compatibility in some way.
You have done something, that it’s worth breaking backwards compatibility over.
Yeah I just forgot how the old stuff worked
Except from 0.x.x to 1.0.0. That one means you’re committed to keeping the API/format stable. At least how I think about it.
For me 1.0 only means that I’ve delivered the software to a paying customer.
Bump the first number when you update to a version that breaks compatibility.
Bump the second number when you make a change that people might want to revert back from
Bump the third number for bug fixes.
I thought the leading number was for when very large changes are made to the core software that make it unrecognizable from a previous version. Like if you changed the render engine or the user interface, or all of the network code.
Woosh
I recently realized: fuck it, just have the build date as the version: 2026.02.28.14 with the last number being the hour. I can immediately tell when something is on latest or not. You can get a little cheeky with the short year ‘26’ but that’s it. No reason to have some arbitrary numbers represent some strange philosophy behind them.
Tried it in the past but ultimately abandoned it, as then release numbers lost all added meaning. I can remember what happened in release 2.0.0 or (kinda) 3.5.0, but what the hell was release 2025.02.15? Why did it break this random function?
I use 2026-03-01-05 too but the -05 does not represent the hour but the number of version i release today. like if i make five commits today, they will be -01, -02, -03, …
