Email or username:

Password:

Forgot your password?
Top-level
jelte

@martin_ueding @nikitonsky With those in mind I'd like to propose shifting the semantics. From last to first:
3rd number (bugfix release): Default. We fixed an issue or improved a feature slightly.
2nd number (Minor release): Proud. We added Cool New Stuff, and all Cool Existing Stuff still works, just the way you like it!
1st number (Major release): Shame. We couldn't be arsed to make new things compatible with existing stuff. Your plugins, scripts, and linked things no longer work. Good luck.

10 comments
0xC0DEC0DE07E8

@jelte @martin_ueding @nikitonsky this is just reframing semantic versioning in pride-shame language, and I love it

Jean-Baptiste "JBQ" Quéru

@c0dec0dec0de @jelte @martin_ueding @nikitonsky I had been thinking shame/pride/shame. Major shame is when you knowingly break something, patch shame is when you had unknowingly broken something.

I once had a team at work will into triple-digit major versions. They sometimes broke compatibility several times a day. It was a struggle to convince them how much of an issue that was, and how no amount of monorepo was going to make people happy with them.

0xC0DEC0DE07E8

@jbqueru @jelte @martin_ueding @nikitonsky we have static versions because we hate ourselves, I guess

:neocat__w: kbity...

@jbqueru @c0dec0dec0de @jelte @martin_ueding @nikitonsky I'm proud when my software doesn't need new features anymore (therefore it's finished) and only requires some maintainence once a year or so.

so shame/shame/normal for me

0xC0DEC0DE07E8

@cybertailor is like to make the suggest making the bugfix/patch level in semver humility
And for kbity, I guess minor version is humility
@jbqueru @jelte @martin_ueding @nikitonsky

Martin Ueding

@jbqueru @c0dec0dec0de @jelte @nikitonsky
With a monorepo you can also go without version numbers altogether. Everything is at always at head.

0xC0DEC0DE07E8

@martin_ueding @jbqueru @jelte @nikitonsky this can break down a little at runtime if you’re deploying components in a distributed manner - but you can always embed the VCS reference as a proxy for version in that case.

Martin Ueding

@c0dec0dec0de @jbqueru @jelte @nikitonsky
That's how I've seen it done. No versions, just git hashes.

0xC0DEC0DE07E8

@martin_ueding @jbqueru @jelte @nikitonsky sorry, work with people in a monopod with absolutely no tracking and they just smack themselves in the forehead regularly and go “oh no, these two components were built from different code and couldn’t figure it out because they talk in our unversioned binary interface language! Better not change anything about our process.”

Go Up