Every developer or dev team can relate -

#dev #development #Tech #techdev

@Natasha_Jay Shit, is my self-esteem just so bad that that's why nothing I've ever made has hit 1.0? 🙃
@disorderlyf @Natasha_Jay (possible) joke aside, yes, it's not unthinkable; I have had, more than once, to force myself to release version 1.0.0 despite inner voices screaming "but shouldn't we do this first? And also that? And those three other things we still have no idea how to even design? We're not ready for 1.0! <wayne's world voice> We're not worthy! We're not worthy!"
@mrrmot @Natasha_Jay tbf I have a lot of unfinished projects. But the more serious concern is more "does my version 0.1.5 project actually 'deserve' that versioning or is it more like a 0.5.9?"
@disorderlyf My problem is usually caused by my maybe excessive desire for stability: I'm too scared to release 1.0 because a part of me just doesn't trust my own design, and I just know that half an hour later I will come up with this great idea that will require whopping API breakage. So... back to not trusting my own work :) @Natasha_Jay

@mrrmot
There's at least one piece of software I used for years that was 0.8.9.xxxx. Only the last 4 digits changed. Maybe a torrent client but 🤔

I think the team couldn't face a 0.9.0001 even as it implied a 1.0.0.
@disorderlyf

@Natasha_Jay @mrrmot There is a part of me that would tempted to have a 0.9.001 version for the memes
@mrrmot @disorderlyf @Natasha_Jay I've used a package at version 0.02 in production, it did the job well with no issues, it genuinely should have been 1.0

@Natasha_Jay

Technically all my code would be something irrational like 0.0.Π²

@Caerfinon @Natasha_Jay

Where’s the imaginary part of the version number? 🤔

@fiee :

That's where you add a plugin framework so you can blame anything that breaks on integrations owned by others.

@Natasha_Jay Could explain Firefox?
@simondassow @Natasha_Jay they used to do the same. I feel like I used firefox 3.6.x for ages until they decided they needed major version bumps all the time
@Natasha_Jay is it bad that all my version increments this year have been the third number?
@flipper :
no that mean your stuff is stable, tightly scoped and you provide frequent security patches.
@Natasha_Jay I'm running Emacs 30.2, which because I remember my history, I know is secretly Emacs 1.30.2. (RMS lopped the 1. off the front some time in the 1980s.)
@wollman @Natasha_Jay the unixen all did this for a while, iirc

@Natasha_Jay @rysiek huh, i’d think of it a little differently…

2 - shame version, we f*cked up the architecture so badly that we had to redo it, incompatibly :(

7 - woot! Pride! We released new features, adding to what we offered before!

123 - mutter, double shame, yeah, that didn’t work did it :(

@Natasha_Jay @rysiek (admittedly the prime number sometimes isn’t that, just a big change and they want a new number, much as you said, but i think my definition is more common)
@Natasha_Jay i almost thought this was euler's number for a second
@Natasha_Jay not to be confused with euler's constant
@Natasha_Jay I always describe that approach as "marketing versioning" 🙃
@Natasha_Jay it gets even worse: https://civfanatics.com/2025/11/12/civilization-vii-update-1-3-0-patch-1/ . For #Civ7 we get a "patch 1" of the minor version....
Civilization VII Update 1.3.0 – Patch 1 - CivFanatics

Firaxis has released a small patch to fix the most urgent bugs in patch 1.3.0. This includes that the AI will use less sanctions, produce GPs correctly, a range of stability improvements and other small fixes. For the complete list and discussion please check here.

CivFanatics - The biggest fan site and community for Civilization fans.
@Natasha_Jay the rust ecosystem should have a bit more pride imho
@Natasha_Jay don't tell everybody. We labeled that semantic versioning. We all agreed on that. It's like TDD which should have been named. We really need to talk to people and get the sales person out of the way.
@Natasha_Jay Tbh, I love software with higher numbers for the third section. I think of it as „maintenance“ not as „fix“ and at least for me its an indicator that devs care about stability and maturity of software.

@Natasha_Jay

I think I just pushed version 0.12.9998

@benpate :
you must own a critical python library.
@Natasha_Jay #hugo 364 releases since 2013 and still hasn’t gotten to 1.0 😂🤣 Little did users know that fast referred to the release and deprecation support cycle
Pride Versioning - Pride Versioning 🏳️‍🌈 0.3.0

Forget semantic versioning, use PRIDE VERSIONING 🏳️‍🌈

@Natasha_Jay "Default version: Shouldn't contain breaking changes by definition, but every once in a while definitely will."
@Natasha_Jay the real semantic versioning
@Natasha_Jay This suggests a LinkedIn versioning scheme, with a single number, incremented on every release with a note saying “I’m proud to announce”
@Natasha_Jay looks at one using CalVer  woaw they're so proud of their proejct   
@freeplay @Natasha_Jay also explains why so many projects are 0.XX.XXX nowadays

@Natasha_Jay :

Major version should be the shame release because you couldn't think of any solution that didn't break back compatibility so you forced a migration on all of your users.

However, this is probably the "current state" slide and semver is the "ideal state" slide.