Yes, and 2 is "I probably broke your favorite API."
Re:ZeroVer: 0-Based Versioning
by still_grokking on Thursday August 12, 2021 @05:04PM
(#28161444)
Probably?
That's regular Semantic Versioning
> Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
> Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public API and how it changes.
> If your software is being used in production, it should probably already be 1.0.0.
Basically, nobody wants to deal with backcompat. Having worked somewhere where we supported stuff more than a decade old, it's not entirely surprising. It's really hard to know what crazy stuff customers are doing with your stuff, and fun new things often die off during the pitch.
Re:ZeroVer: 0-Based Versioning
by aabbcc1241 on Thursday August 12, 2021 @08:58PM
(#28163965)
think of react-native being used in production for years while it's in 0.x.x
Honestly, for my one-man projects I use 0. to indicate "there is absolutely no backwards compatibility guarantees because I'm still fucking around" and 1. to indicate "this is in prod and I'm confident about it" (with attendant discipline on how semver major/minors are supposed to be used).