Shame-antic versioning
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.
It’s logical if Linus has some numbers autism
idk for me it’s easier to rember ex xdna was merged on 6.14 than 2.253
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
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.
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.
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
1.21 to 1.211
So +190 increment is totally ok for you, but +1 sometimes “didn’t make sense”. IT DOESN"T MAKE ANY SENSE! Oh, and you can use letters. 1.21 -> 1.21a looks MUCH more explanatory for your purposes than “+1 is too harsh increase, so I’ll increase on 190!”
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
I do that too sometimes lol but I’m just not a fan
if it were actual releases, yeah totally. but it’s just temporary files
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.
Can you immediately tell? Do you memorize the last day you released? Do you release daily? There’s definitely some benefit to making the version equal to the date, but you lose all the other benefits of semver (categorizing the scope of the release being the big one). That’s not a strange philosophy, it’s just being a good api provider.
You’re right. I’m looking at it through a very limited scope: nightly releases. I’ve been working with “latest” so long, I forgot actual versions exist.
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, …
The philosophy is pretty straight-forward. I don’t know why the world is pretending it’s difficult.
Chesterton’s Fence, but for workflows you don’t understand.
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!
I guess …x. means NOTHING to you… ;-)
