Every developer or dev team can relate -

[h0ru2@cyberplace.social]

@Natasha_Jay "Default version: Shouldn't contain breaking changes by definition, but every once in a while definitely will."

[hashbangperl@hachyderm.io]

@Natasha_Jay the real semantic versioning

[hashbangperl@hachyderm.io]

@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

[hashbangperl@hachyderm.io]

@wollman @Natasha_Jay the unixen all did this for a while, iirc

[skitt@mastodon.social]

@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”

[freeplay@wetdry.world]

@Natasha_Jay looks at one using CalVer woaw they're so proud of their proejct

[gwenthefops@transfem.social]

@freeplay@wetdry.world @Natasha_Jay@tech.lgbt also explains why so many projects are 0.XX.XXX nowadays

[offline_and_free@todon.nl]

@Natasha_Jay :

Major version should be the shame release because you couldn't think of any solution that didn't break back compatibility so you forced a migration on all of your users.

However, this is probably the "current state" slide and semver is the "ideal state" slide.

[offline_and_free@todon.nl]

@fiee :

That's where you add a plugin framework so you can blame anything that breaks on integrations owned by others.

[offline_and_free@todon.nl]

@benpate :
you must own a critical python library.