Hacker News new | ask | show | jobs
by dnautics 1772 days ago
> I'm a one man shop though so I never branch for major/minor releases.

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).
2 comments
failrate 1772 days ago
Yes, and 2 is "I probably broke your favorite API."
link
still_grokking 1771 days ago
Probably?
link
gowld 1771 days ago
That's regular Semantic Versioning

https://semver.org/

> 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.

link
zamalek 1771 days ago
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.
link
aabbcc1241 1771 days ago
think of react-native being used in production for years while it's in 0.x.x
link