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.
It’s logical if Linus has some numbers autism
Hmm, guy who wrote his own kernel because he didn’t like the ones that existed. I’m sure he’s totally neurotypical. /s
idk for me it’s easier to rember ex xdna was merged on 6.14 than 2.253
See that’s totally logical, but it makes more human sense than computer sense.
Well that explains why I’m on version
0.0.7899999999998765
deleted by creator
Most of the mistakes they have to fix are incorrect version numbering.
AI slop bbyyyyyyy!!!
Weak humans would use 250 million years, strong AI can slop it in 1 year.
/S
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.
Wow a little bit of math is a dangerous thing
And here I was holding my breath for the legendary 0.0.7899999999998766. Thanks for ruining all my dreams.
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, …
that’s with the assumption that the smallest increment was used every time
I sometimes increment things by adding the next decimal place
note: I am not a developer, just a dude making tools at work. but I somehow always end up incrementing something now and then from 1.21 to 1.211 because I wanted to avoid the “1.21 new actually newest” situation and bumping to 1.22 didn’t make sense. it’s like temporary versioning for me, WIP files
deleted by creator
so I actually use various different systems depending on my mood that day.
maybe I add a dash, maybe I use another decimal, maybe I use alpha characters.
none of it matters because they’re wiped out a few hours later
Sub version tags make sense but for the the love of pie if you’re going to use a number at least separate it from the others, like
1.21-1
You need to cast that float.
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.
Python agrees.
Sir…
Lowkey how I version number personal mini-projects and small things I roll out for my team.
I guess more like:
x… “huge new feature, scope expansion, or cool shit.”
.x. “small feature, or fixing a serious bug” …x “testing something. Didn’t work. Try again +1.”I’m not ashamed it didn’t work. I swear!
minecraft being on 1.21.11 (i think)
deleted by creator
fucking hilarious! I needed to laugh. Thanks @cm0002@infosec.pub this made my day
For the shame version isn’t updating the version number admitting there is new changes?
slight disagree: proud version is actually when you become so disillusioned with your old code that you throw it all out and start again
Version 2.0? You mean an entirely new program, right?
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.
But are you proud of that large change?
If I were the author of GIMP I wouldn’t be
B’DUM’TSH
In semantic versioning the first number is for any change to a public API that is not backward compatible. It could be incredibly small, like fixing a typo, but if it changes the API your users are using in an incompatible way, you’re supposed to bump that number.
oh yeah
