Don MacKinnon · Dec 22

lol shame versions

Reddy · Dec 23

Been proudly versioning for every update so far because each one breaks compatibility 😌

SmilerRyan · Jan 2

without knowing what symanteic versioning is (too confusing for me, and not looked into it really) this just makes more sense.

reggie seidman · Dec 22

shamever

Philipp Pohl-Krüger · Dec 22

I propose we *actually do* semantic versioning instead of pride versioning, which seems to be the default 🙃

Ivan “CLOVIS” Canet · Dec 22

This is how the Linux kernel is versioned, no?

Nazieb · Dec 23

we used to have the Sentimental Versioning github.com/dominictarr/...

Alpha · Dec 23

I propose we add another term at the beginning which increments when things get out of control and you need to rewrite everything from scratch.

Zach 🇺🇦🇪🇺 · Dec 23

Every other program would have a version like 1.2.643684463753

L Break Into Program · Dec 22

Not enough shame digits imho.

José Ibáñez 🇵🇸 · Dec 22

I am releasing 0.1.947 following that convention

Rogério Tavares Gasi · Dec 22

Humble teams staying on 0.12.x forever and egocentric teams going to release 55.0.x pretty soon

Kris Nuttycombe · Dec 22

All of a sudden I am, for the first time ever, wishing that everyone just used the Haskell PVP. (pvp.haskell.org).

tommyjones.bsky.social · Dec 24

I just use the release date with an extra digit for first day mishaps

Allan Deutsch · Dec 23

They are the same thing 😂

Wes · Dec 22

Lol, stay humble React Native

Alec Lloyd Probert · Dec 22

Risky. Being proud too quickly would ++ the first digit af

SylvieTG · Dec 22

I think you've cracked Chrome's version sheme.

Tizzo · Dec 23

I think I've been doing it this way the whole time 🤷‍♂️😂

Kerkness · Dec 22

All my releases are shameful

Jonathan Sanderson · Dec 22

I 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.

Satans favorite imp · Dec 24

What's the difference? Also, you guys version stuff, you don't just yolo to prod?

Immo Landwerth · Dec 22

@jeffhandley.com

phiidev (real) · Dec 29

isn't this how you're supposed to do it?

Prakash Advani · Dec 22

Why not have Year.month.bugfixes

designer de stacktrace · Dec 21

And no breaking changes please Use a new name for new behaviors

Glenn · Sep 4

Is... that... not how we've been doing this?

Ugur Bulut · Dec 23

'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.

David Darnes · Dec 22

Wait, is this _not_ the default??

(λ. borkdude) · Dec 21

This is how I version, except the shame just keeps incrementally increasing

Upthorn · Dec 23

They are the same system.

Kenton Vizdos · Dec 22

I propose “idfk versioning” In terms of symver, Major never changes Minor gets updated whenever the hell you want Patch? Who needs patches, constant 0

DmR · Dec 22

And nobody wants version X.00