4 ms·

Projects using semver try not to do breaking changes, which is why they don't change major versions often. It works really well for libraries and APIs, but in

Projects using semver try not to do breaking changes, which is why they don't change major versions often. It works really well for libraries and APIs, but in my experience it doesn't work well for end-user-facing products. If you look at npm packages, a lot use semver.

dartos 2y ago
in semver, if your major version is 0, then any change can be breaking, which, imo, is why semver projects stay pre-1.0 for so darn long. So even with semver, pre major version 1 is pretty much meaningless.