2 ms·
> You're basically suggesting reimplementing semver in a clunkier way. Just bump the major version but continue supporting the old major version with security r
by lmm 5y ago
> You're basically suggesting reimplementing semver in a clunkier way. Just bump the major version but continue supporting the old major version with security releases etc.
> This is a solved problem, it's just that some library maintainers don't practice proper communication of breaking changes.
It's not just a communication problem, it's also the way that a lot of language tooling works. For example on the JVM you can (mostly) only have a single version of a given (fully qualified) class on a given application's classpath, so it's quite important for incompatible new versions of a library to use a completely new set of class names - thus you'll see e.g. commons-lang3 using org.apache.commons.lang3 alongside commons-lang using org.apache.commons.lang.