How about something new: release only backward-compatible updates unless absolutely necessary.
For real. If its not acting the same, then its not the same thing, give it a different name and release your 0.1. I guess maybe we run out of namespace with this methodology? Suddenly we end up with software named axsladkjfaksldjf, and then hackers start camping on axsladejfaksldjf
The name space is not a problem, in my opinion. If you have a library sdaffj, and you want to release a new, incompatible version, release it under the name sdaffj2, next incompatible version under name sdaffj3, etc.
I think codemod is probably one such tool: https://github.com/facebook/codemod
Re:Software Is Drowning the World
by raverbashing on Sunday January 10, 2021 @09:43AM
(#25715026)
Or you know, library deprecates "easy way of doing something" replacing it with "weird and convoluted" way of doing this again without any guidance of how to do the old thing
And unless the old way was genuinely bad/hard, why deprecate?
Like python’s “2to3”.
It’s not a magic bullet; the developer still benefits from thorough testing, but I think changelogs could stand to improve in a lot of projects.