Niki Tonsky@tonsky.meI propose we replace semantic versioning with pride versioning21/12/24, 7:07 pm·735 reposts·2.5K likes
SmilerRyan@smilerryan.bsky.social2 Jan 2025without knowing what symanteic versioning is (too confusing for me, and not looked into it really) this just makes more sense.
Philipp Pohl-Krüger@matheus23.com22 Dec 2024I propose we *actually do* semantic versioning instead of pride versioning, which seems to be the default 🙃116
twentyonetwelve.bsky.social@twentyonetwelve.bsky.social22 Dec 2024No, they bump the first number when they run out of digits to count the 2nd number.13
Ponder@ponderstibbonsuu.bsky.social22 Dec 2024Ironic, considering Linus Torvalds built the most widely used version control system in the world.
Nazieb@nazieb.com23 Dec 2024we used to have the Sentimental Versioning github.com/dominictarr/...github.comgithub.com8
Alpha@alphatheskunk.bsky.social23 Dec 2024I propose we add another term at the beginning which increments when things get out of control and you need to rewrite everything from scratch.1
Zach 🇺🇦🇪🇺@zachrid.bsky.social23 Dec 2024Every other program would have a version like 1.2.643684463753
Ponder@ponderstibbonsuu.bsky.social22 Dec 2024You can always add a build number if you break something in an ungodly manner.1
Rogério Tavares Gasi@rodja.bsky.social22 Dec 2024Humble teams staying on 0.12.x forever and egocentric teams going to release 55.0.x pretty soon156
Mr. Jason@herr-jason.bsky.social22 Dec 2024Marketing would also drive that first number into the stratosphere. Also, it'd be infinity.x.0 because "We never ship bad code"...2
Kris Nuttycombe@nutty.land22 Dec 2024All of a sudden I am, for the first time ever, wishing that everyone just used the Haskell PVP. (pvp.haskell.org).
tommyjones.bsky.social@tommyjones.bsky.social24 Dec 2024I just use the release date with an extra digit for first day mishaps
Alec Lloyd Probert@graphieros.npmx.social22 Dec 2024Risky. Being proud too quickly would ++ the first digit af
Jonathan Sanderson@jjsanderson.bsky.social22 Dec 2024I think this is pretty much how I work, only with an added layer of sometimes starting a whole new repo in the hope of escaping the taint of the current one.19
Satans favorite imp@coffeepot.satan.social24 Dec 2024What's the difference? Also, you guys version stuff, you don't just yolo to prod?GIF
designer de stacktrace@souenzzo.com.br21 Dec 2024And no breaking changes please Use a new name for new behaviors1
Kris Nuttycombe@nutty.land22 Dec 2024This is an absolutely terrible idea. Infinite backwards compatibility is a large part of why software sucks.13
Kris Nuttycombe@nutty.land22 Dec 2024How many Windows exploits will it take for you to recognize that this doesn’t actually work, and is in fact horrifically costly to humanity?5
Ugur Bulut@ugurbulut.bsky.social23 Dec 2024'If it works, don't touch it versioning' is the way to go. Worked on the first try, and it's been 0.1.1 for 3 years.
(λ. borkdude)@borkdude.bsky.social21 Dec 2024This is how I version, except the shame just keeps incrementally increasing11
Kenton Vizdos@kv.codes22 Dec 2024I propose “idfk versioning” In terms of symver, Major never changes Minor gets updated whenever the hell you want Patch? Who needs patches, constant 0