Every developer or dev team can relate -
-
Every developer or dev team can relate -
@Natasha_Jay is it bad that all my version increments this year have been the third number?
-
Every developer or dev team can relate -
@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.)
-
Every developer or dev team can relate -
@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 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)
-
Every developer or dev team can relate -
@Natasha_Jay i almost thought this was euler's number for a second
-
@Natasha_Jay i almost thought this was euler's number for a second
@Natasha_Jay not to be confused with euler's constant
-
Every developer or dev team can relate -
@Natasha_Jay I always describe that approach as "marketing versioning"
-
Every developer or dev team can relate -
@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....
-
@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
-
Technically all my code would be something irrational like 0.0.Π²
Where’s the imaginary part of the version number?
-
Every developer or dev team can relate -
@Natasha_Jay the rust ecosystem should have a bit more pride imho
-
Every developer or dev team can relate -
@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.
-
Every developer or dev team can relate -
@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.
-
Every developer or dev team can relate -
I think I just pushed version 0.12.9998
-
Every developer or dev team can relate -
@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 -
Every developer or dev team can relate -
-
Every developer or dev team can relate -
@Natasha_Jay "Default version: Shouldn't contain breaking changes by definition, but every once in a while definitely will."
-
Every developer or dev team can relate -
@Natasha_Jay the real semantic versioning
-
@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 @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 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
