Re:Chronologic Versioning: No more arbitrary version updates...
by slowmovintarget on Thursday January 02, 2020 @12:54AM
(#21933309)
To paraphrase Rich Hickey: "Just use a different name."
Compatibility of APIs is retained if you require less or provide more. Breaking changes happen when you require more or provide less. Don't do it. Add a new and different function that requires more or provides less. Keep the old one. You now have a backward compatible interface.
I think a more modular versioning standard might be good as semantic versioning can be very helpful in certain projects like libraries.
Like if your project has x abstract property then include x. and y for a x.y versioning scheme.