Every developer or dev team can relate -
-
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
-
Every developer or dev team can relate -
@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”
-
Every developer or dev team can relate -
@Natasha_Jay looks at one using CalVer woaw they're so proud of their proejct
-
@Natasha_Jay looks at one using CalVer woaw they're so proud of their proejct
@freeplay@wetdry.world @Natasha_Jay@tech.lgbt also explains why so many projects are 0.XX.XXX nowadays
-
J jwcph@helvede.net shared this topic
