1.1k
u/MayIHaveBaconPlease Mar 03 '25
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
314
Mar 03 '25
Google Play devs after updating app to 1.56.423: "To ensure the best experience in App name, we have brought you the latest bug fixes and performance improvements."
41
13
4
2
3.7k
u/WW_the_Exonian Mar 03 '25
Hence my app at version 386.0.0
1.5k
u/lemons_of_doubt Mar 03 '25
and my app at version 0.2354.0
yay government work!
683
u/nickwcy Mar 03 '25
why my app version is 1.0.27592 …
369
u/hanotak Mar 03 '25
Your app reached its 1.0 release?
462
→ More replies (1)26
u/SaltyLonghorn Mar 03 '25
All 1.0 did was give you a number between 1 and 9. Its been nothing but headaches since we went higher.
→ More replies (1)25
62
u/Honza368 Mar 03 '25
Behold my app at version 127.0.0.1
→ More replies (2)29
65
u/RoseSec_ Mar 03 '25
That’s a lot of breaking changes
191
u/andreortigao Mar 03 '25
You up you major version because you introduce breaking changes.
I up my major version because every change I make breaks something.
We're not the same.
24
3
u/random-lurker-456 Mar 03 '25
If you're not rewriting your 1000 lines of actual code every day because you found 17 ways to make something neater while bugfixing the previous release are you even programming ?
8
→ More replies (5)5
u/Mortimer452 Mar 03 '25
Mine is 0.0.9653872
6
1.6k
u/lOo_ol Mar 03 '25
I think this is how everyone does it, but never truly put it into words like that, like second nature.
28
u/Mortimer452 Mar 03 '25 edited Mar 03 '25
We did this for many years but eventually got tired of the somewhat arbitrary increments and settled on YYYY.MM.DD.RR (RR = revision# in case we had multiple releases in a day)
39
u/GateauBaker Mar 03 '25
The problem with just using the date is that it makes it harder to backtrack to a previous version with a specific feature in mind. It's easy to separate in your mind what changed between 1.0.0, 2.0.0, and 3.0.0, but not three arbitrary dates. Of course if all anyone cares about is the latest version go ahead and just use the date.
6
u/tekanet Mar 03 '25
Unfortunately I see lot of:
major: bump up if you want to collect another round of payments from users
→ More replies (14)2
786
u/alex_tracer Mar 03 '25
Alternative meaning:
"Things got broken, but new features may compensate that"
"Maybe something broken, but should not be a big deal"
"We promise we did not break new things. Maybe"
380
u/_-Smoke-_ Mar 03 '25
We all know it's actually
"Major work and primary features"
"Bug fixes and minor features"
"Management wants to see progress so we changed nothing of significance so bigger number make them happy"
144
u/Titaniumwo1f Mar 03 '25
V1.2.68: bugs fixed
Management: Hmm, we're stuck at V1.2.68 for too long, please bump a version to create an illusion of progression.
V1.2.69: bigs fuxed
47
20
3
Mar 03 '25
1 is like a coin toss.... either you get something much better, or they went down a path of self-destruction and you better hope you backed up the old version.
→ More replies (1)3
u/Phatricko Mar 03 '25
This took me forever to find because it looks like the real site got hacked or something but there is a schema out there that supports making the number whatever feels good 😌
https://web.archive.org/web/20200414234137/http://sentimentalversioning.org/
136
u/LeyendaV Mar 03 '25
56
u/darexinfinity Mar 03 '25
Implying we don't fuck up multiple times a day.
→ More replies (5)19
u/iner22 Mar 03 '25
Then just add an _# to any hot fixes? Surely you wouldn't fuck up more than 9 times in a day, right?
... right?
69
u/PerhapsJack Mar 03 '25
Just always be version 1.0.0.
29
u/veloxVolpes Mar 03 '25
I don't normally like this format, but this was quick and compelling information. Thanks for sharing.
13
7
6
→ More replies (3)3
13
u/AnarchistBorganism Mar 03 '25
I usually go Major.Minor.YYYYMMDDhhmmss.SSN.BuildNumber
→ More replies (1)15
→ More replies (2)2
66
52
u/N238 Mar 03 '25
Practically an overhaul
New features but no radical changes
We fixed a bug (or found a new loophole to spy on you better)
35
u/Janneman96 Mar 03 '25
Should be
major; breaking changes
minor; new features (without breaking changes)
patch; bug fixes
But yeah MongoDb did a breaking change on a patch update... Luckily we have automated tests.
10
70
u/SpaceCorvette Mar 03 '25
I'm shocked at how many people don't think this is humor lmao. I hope you guys aren't maintaining libraries or APIs
79
u/urzayci Mar 03 '25
Narrator: they were maintaining libraries and apis
5
u/sschueller Mar 03 '25
Thank you for giving me job security trying to figure out why my +10m lines of code don't work after your patch release update....
5
u/urzayci Mar 03 '25
Not me personally, I don't program enough to have anything to maintain, but I'll pass the message on
153
u/ChChChillian Mar 03 '25
TIL this isn't what it means for everyone.
236
u/YellowJarTacos Mar 03 '25 edited Mar 03 '25
Semver is fairly standard in the a few language ecosystems and makes a lot of sense.
Major: any breaking change
Minor: new features / API changes
Patch: bug fixes
It works well - especially requiring any breaking change to be a major version bump makes it clear to devs when they need to pay attention to updates.
18
u/nickwcy Mar 03 '25
I always annoyed by Python releases, minor version change should not be breaking
→ More replies (1)8
u/JanEric1 Mar 03 '25
They arent breaking to the the language itself.
But they do break the C api and standard library.
41
u/ChChChillian Mar 03 '25
However, one thing I didn't have to learn today is that some people don't understand what the "humor" part means in the name of the sub.
55
u/YellowJarTacos Mar 03 '25
Your comment wasn't funny so I assumed it was serious.
→ More replies (5)→ More replies (11)5
14
Mar 03 '25
X.Y.Z, where
X: Broke stuff on purpose
Y: Didn't break anything, I promise
Z: Broke stuff by accident
12
u/Classy_Mouse Mar 03 '25
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
7
12
u/Vicus_92 Mar 03 '25
If your version number looks like an IP address, you're doing something wrong.
Regards, A Sysadmin.
→ More replies (1)2
u/holchansg Mar 03 '25
Thats why i use emojis, just deployed the version 👆🥵.👌👀.🙏🤦♂️💩
Sadly wasn't a very good release hence the 💩
→ More replies (1)
20
u/thanatica Mar 03 '25
Meanwhile, browser version going up for 3 minor bug fixes and 1 change nobody even asked for.
9
u/zonz1285 Mar 03 '25
<major changes/features>.<minor changes/features>.<small security updates>.<opps I forked something up>
6
11
5
5
u/Grandmaofhurt Mar 03 '25
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?
→ More replies (1)
5
u/Anaxamander57 Mar 03 '25
Honestly, not a bad explanation. Alternatively:
HAHA FUCK THE USERS . Normal Release . hehe oops
5
u/H33_T33 Mar 03 '25
Is it weird that I feel proud bumping the numbers at all? 2.0.0 to 2.0.1 or so just feels so good… probably because I’d have spent weeks trying to fix just one bug.
5
4
u/SeaNational3797 Mar 03 '25
Minecraft mods are so much easier
x.y.z
x: bump when Minecraft version increases
y: bump for major update
z: bump for minor update
4
4
4
3
3
3
3
u/ThE_reAl__ Mar 03 '25
2
u/ccAbstraction Mar 04 '25
I love this because it unironically means you get to bump the major release number by 1000 when you are proud of a release.
TLDR and the blog post the video talks about: https://antfu.me/posts/epoch-semver#epoch-semantic-versioning
3
3
u/cloudd901 Mar 04 '25
Currently, I have a production app sitting at v0.12.23. Not very proud of it.
4
u/ImReallyFuckingHigh Mar 03 '25
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.
→ More replies (2)
2
2
2
2
u/ZaraUnityMasters Mar 03 '25
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
2
u/revenezor Mar 03 '25
The numbers shouldn’t be zero-padded. It should be 1.9.16, not 1.9.016. Otherwise you’re implying a limit to the number of times you can increment.
For example, if you’re at 1.9.016 now, then what comes after 1.9.999?
If 1.9.1000, then why wasn’t it zero-padded to 1.9.0016?
If 1.10.000, then why wasn’t the second number zero-padded as well (e.g. 1.09.016)? Not to mention you’ve arbitrarily forced yourself to bump the second number instead of the third.
2
2
2
u/Imthemayor Mar 03 '25
I wish Nintendo followed this
"Update your Switch to version 10.0.0!"
Patch notes:
General system stability improvements
2
2
2
u/Symbology451 Mar 03 '25
As a newbie and based on this system, the highest version I've managed is 0.0.253
2
2
Mar 03 '25 edited May 01 '25
important summer touch melodic complete tender yoke aback scale angle
This post was mass deleted and anonymized with Redact
2
u/SuperbSouma Mar 03 '25
When it starts looking more and more like an IP address, you know your work is still valued.
2
u/DoNotMakeEmpty Mar 03 '25
Just use converging version numbers, like at each update, add another digit to converge to an irrational number like pi or e. Donald Knuth has a good taste of versioning.
2
u/Flaky_Arugula9146 Mar 03 '25
If I increase the default version, should I reset the shame version to 0?
2
2
u/ChaplainGodefroy Mar 03 '25 edited Mar 03 '25
Life hack from the World of Tanks devs: drop first zero after years of "beta" and now you have proud number!
2
u/DifficultInspector Mar 03 '25
First number, massive changes that break all previous compatibility Second number, smaller change that actual add functionality but introduces new bugs Final number, small changes to fix the problem caused by the previous change
2
2
u/saltedhashneggs Mar 06 '25
Default version aka show my boss progress despite him having no clue how any of this works, but "the number goes up" so great, bonuses for everyone.
2
2
u/KingTrumpsRevenge Mar 03 '25
Looks like everyone is talking about the real version the dev team uses internally and not the one used to placate the business side.
a.b.c.d
a - CEO's new initiative b - When we need a new marketing push c - When a client wants to feel special d - Unique id linking to useful version number dev team uses.
2
u/willisbetter Mar 03 '25
this implies that mojang actually havent been proud of a minecraft release since 2011 because they havent bumped up to 2.0 yet, its still on 1.21.5
→ More replies (1)
1
1
1
1
1
1
u/badgersruse Mar 03 '25
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.
1
1
1
u/solar1333 Mar 03 '25
This is....not what those actually are.
It goes major, then minor, then patch.
But you do you ig. As long as you doing you isn't spreading misinformation.
Edit: I think there are multiple ways to do it but I'm pretty sure this is the most common from what another comment said
1
u/reevesjeremy Mar 03 '25
0.9.999 means I was never proud enough to promote you. And my next version will be 0.9.9991. Because I just can’t.
→ More replies (3)
1
1
1
1
u/Meta-Four Mar 03 '25
And then there's my company, releasing a .1 as the fourth column the day after I deliver it to a customer.
1
1
1
u/ADwards Mar 03 '25
Well, it's better than one project I follow, which just uses it like one long number.
1
1
1
1
u/OneWholeSoul Mar 03 '25
It's this basically it?
For me it's "Major Feature Update/Added Functionality" - "Functioning Adjustment" - "Bugfix."
1
u/just-here-4-memes Mar 03 '25
Almost relevant xkcd. I feel like they should have addressed this more directly at some point but couldn't find anything myself.
1
u/BlizzTube Mar 03 '25
I will live by this now. I don’t program really much (cuz I suck at it) but when I do I will use this
1
1
1
1
1
1
u/YesterdayDreamer Mar 03 '25
Chromium devs are really proud of having increased the radius of the dots in the menu icon by one pixel for screens with 150+ dpi. Version number bumped from 135 to 136.
1
u/i_amsquidward Mar 03 '25
This is perfect and correct. Coders are proud after finishing massive overhauls that paid off. Its normal work to fix bigish things every couple months, but its not huge. And the shame bits are tiny and only noticed by users because coder didnt plan that test case
1
u/SNappy_snot15 Mar 03 '25
test1.c test2.c test3.c.
aren't you good enough to tell which one's better?
1
1
1
u/biathalounge Mar 03 '25
Is this not actually how releases are supposed to be numbered for anything?
1
1
u/Kromieus Mar 03 '25
Linux kernel when: “The second number is getting too big, let’s bump the first one up by one instead and reset the second one “
1
1
1
u/OrnerySlide5939 Mar 03 '25
If people actually did this, we would have 0.1.99999 for basically every piece of software. What i always hear is "i wish we had more time"
1
1
u/ihave7testicles Mar 03 '25
This is the most real and truthful thing I've seen in a long time and it's not even humor. It's just true
1
u/ohshaughnessy Mar 03 '25
Ha! That feels more real than semver!
Sometimes I let my software follow the old school DNS zone serial number convention: YYYYMMDDNN, where NN is how many changes you’ve made that day. (I’ve never hit 99, fortunately.) If you’re not releasing it to anybody outside your small team, this can work great and save you from the introspective judgement calls of “default or bug fix?” (“impish or admirable?!”) Sometimes you just need to bump the version, and sortable timestamps are handy and build in some clear metadata.
1
u/Dangerous_Gear_6361 Mar 03 '25
I thought it was depending on how much the new release will potentially mess with compatibility. When the system is rewritten and will break any and all plugins, you make a major number update. When it is fairly significant but won’t break all plugins, you make a medium number update. When it potentially won’t affect any plugins, you make a minor number update.
1
1
1
u/Not_Artifical Mar 03 '25
I add letters when I’m too embarrassed to admit the bugs that were fixed.
1
u/breno_hd Mar 03 '25
1 What management thinks I'm doing 2 What my team thinks I'm doing 3 What I'm actually doing
1
u/the4fibs Mar 03 '25
what does that make the yyyy-mm-dd people? i thought i was supposed to feel better than them...
1
u/mazzicc Mar 03 '25
I liked my last company’s system.
Year.Quarter.Sprint
You knew exactly how long it was since anyone updated based on the release they had.
1
u/ghengis_flan Mar 03 '25
wow okay. all my code is version 0.1. want anything more? look at github's history.
1
u/rosuav Mar 03 '25
Of course, at some point you get to 2.7.182 and then you realise that the only valid way to continue is 2.7.182.818...
1
1
1
u/Luxalpa Mar 03 '25
Start working with Rust and you'll learn semver. Because cargo, the Rust build tool, actually depends on you versioning your packages correctly.
1
u/errorg Mar 03 '25
Okay, small tangent but we're dealing with a software update that involves a number like 1.13 being a later version than 1.9
Does that feel wrong to anyone else because it drives me crazy.
→ More replies (1)
1
u/AshMost Mar 03 '25
I'm no programmer, but I do write the occasional script for work. I usually use this for versioning: 2025.03.03-1. The number after - gets bumped with new developments for that day.
How disgusting am I?
1
u/cn-ml Mar 03 '25
Semver is thing, and it is pretty good. increment the first only if you introduce a breaking change, and dependents need to perform an update. This dependents can safely use 3.1.5 without accidentally breaking at version 4. Minor for new features and patch for Bugfixes.
1
u/earthwormjimwow Mar 03 '25
At least be man enough to limit your shame versioning to only 2 digits...
1
u/baggyzed Mar 03 '25
Nah, the proper scheme is major.minor.patch.hotfix.
This way, you get a chance to disguise some of the hotfixes as patches, and avoid the embarrassment. However, this also doubles (or triples) the amount of embarrassment for hotfixes. Gotta keep those devs on their toes.
1
1
u/IronGin Mar 03 '25
I'm just annoyed with version 1.0.97 being a older version than 1.0.103...
My mind reads 0,97 > 0,103
1
u/yiliu Mar 03 '25
From the user perspective, in reverse order: "who gives a shit?", "who gives a shit?", and "ahh fuck now I have to redo everything"
1
1
u/ultralaser360 Mar 03 '25 edited Mar 03 '25
Memes aside semver sucks, I do:
Marketing.
Major changes / new features ( every change is breaking, no reason to bump it up )
Minor changes + bug fixes
Or
Marketing
Major * 100 + minor
Bug fixes

6.8k
u/PandaNoTrash Mar 03 '25
That is exactly how I feel and how I number releases.