ifYouDidntKnow
Friday, 14 Mar 2025
Exclusive insights, data, and analysis for financial market experts.
Search
Have an existing account?
Sign In
Hence my app at version 386.0.0
That is exactly how I feel and how I number releases.
I think this is how everyone does it, but never truly put it into words like that, like second nature.
Alternative meaning:
1. “Things got broken, but new features may compensate that”
2. “Maybe something broken, but should not be a big deal”
3. “We promise we did not break new things. Maybe”
TIL this isn’t what it means for everyone.
[Year.Month.Day](http://Year.Month.Day)
That… is actually exactly how I have always done it.
I’m shocked at how many people don’t think this is humor lmao. I hope you guys aren’t maintaining libraries or APIs
Meanwhile, browser version going up for 3 minor bug fixes and 1 change nobody even asked for.
Strongest semver fan vs weakest “the last number got too big” enjoyer
This is exactly how we number releases at work.
<major changes/features>.<minor changes/features>.<small security updates>.<opps I forked something up>
1. Practically an overhaul
2. New features but no radical changes
3. We fixed a bug (or found a new loophole to spy on you better)
The app developer writing the changelogs:
1.0.1: Bug fixes and performance improvements
1.1.0: Bug fixes and performance improvements
2.0.0: We’ve updated the app to bring you the latest bug fixes and performance improvements!
2.0.1: Bug fixes and performance improvements
They call me 007 😎🔫
Yep at my company we’re on 10.0.22390.
I’m not on software engineering, I’m an engineer and do lots of validation so it’s likely that’s its not they’re bad programmers, I’m just really good at breaking things. Gotta put yourself in the mindset of what’s the dumbest, most nonsensical, and/or malicious entry or set of operations I can attempt with this feature?
All of my projects on version 0.0.375267251
You can also optionally add an initial 1. to represent it being the first edition of the software without any intention to make a 2nd edition.
I’m looking at you Minecraft, Terraria, and Stardew Valley.
My app would be 1.268.12996v
what about gluttony versioning
Why is this so accurate?
You guys are overthinking this. Just bump the version randomly on your PR and wait for one of the reviwers to tell you what version it should be
2025.3.0
I think every “git push” I do is followed by several shame releases.
The secret fourth number where it’s every time I hit “build” is the real shame number
Newer to programming but additionally I was told the last 3 numbers you increment per “fix/change” even if it’s one update.
So like I made 16 changes to 1.9.0 so now it’s 1.9.016
Nah i like Year. Mth.Day
I assume this but Microsoft bros seem to reinvent everything .
I once tried to explain to an engineering director (as support/marketing) to have our first actual release version be 3.x.x, because no one has any confidence in a 1.x.x version so sales is harder and support calls more common. He stubbornly insisted that it must be 1 because it was our first released version.
We didn’t release on 3, but got to 3 in just a few weeks not because customers were nervous but because 1 and 2 were buggy as shit.
just hit 3.0 on my beta recently, woo!
shamever > semver
Damn I didn’t know there were programmers in 123 AD.
Honestly, not a bad explanation. Alternatively:
HAHA FUCK THE USERS . Normal Release . hehe oops