3 ms·
Developers have been afraid of 1.0.0 for a while, in defiance of the semver spec [1], in particular in the Rust ecosystem, but being afraid of 0.1.0 is a whole
by remram 1y ago
Developers have been afraid of 1.0.0 for a while, in defiance of the semver spec [1], in particular in the Rust ecosystem, but being afraid of 0.1.0 is a whole new level. Wtf. I guess 0.1 has become the new 1.0 after years of mis-versioning.
Those coreutils are being included in Ubuntu, call them 1.0! It's fine, you still have a countable infinity of version numbers if you need to make changes, even incompatible ones!
[1]: https://semver.org/#how-do-i-know-when-to-release-100 https://semver.org/#how-do-i-know-when-to-release-100
> If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backward compatibility, you should probably already be 1.0.0.
- eviks 1y agoThat just highlights the major flaw in semver where marketing version and compatibility signal are in a single number. And their guidance on 42 is bad as well, which compounds the fear.
- remram 1y agosemver is very open about not having, or being, a "marketing version". It is its entire reason for being.
- braggerxyz 1y agoYeah I feel you. So many projects do this nonsense.
- steveklabnik 1y agoThat’s a FAQ section, not the spec itself, so it’s not really in contradiction to the spec.