alt Hacker NewsIn libraries, 0.x is for when you’re still figuring the API out. Basically you’re saying that no API is stable at this point, and you’re not doing semver yet, and anything can change.
Naturally, the users should treat those libraries as beta versions and only use them in production at their own risk.
> you can’t properly declare a new release to be a feature or bugfix
0.5.0 vs 0.4.1?
0.5.0 is a new feature 0.4.1 is a bugfix
In practice, 0.5 can be assumed to be breaking but then how do you specify non breaking new features? 0.4.1? Moving to 1.0.0 makes things a lot clearer. For breaking, just go to 2.0.0 etc