Gregory's Server@jelte @martin_ueding @nikitonsky this is just reframing semantic versioning in pride-shame language, and I love it
|
9 comments
@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.  @jbqueru @jelte @martin_ueding @nikitonsky we have static versions because we hate ourselves, I guess  @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 @cybertailor is like to make the suggest making the bugfix/patch level in semver humility  @jbqueru @c0dec0dec0de @jelte @nikitonsky @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. @c0dec0dec0de @jbqueru @jelte @nikitonsky @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.” |
@c0dec0dec0de @jelte @nikitonsky
Oh yes indeed. That's awesome!