Am Tue, 17 Nov 2020 01:11:38 +0100 schrieb "Dr. Arne Babenhauserheide" <arne_...@web.de>:
> The only way that works is to avoid breakage on update — except for > the few cases where it is truly unavoidable. Well, and as long as the change can be reverted when the community has a thoughtful discussion with those who did the work, the world is wonderful. Even if the devels insist they did the right thing, but the discussion brought up way to mitigate the fallout, all is fine. I even get the feeling of being part of a great community through this very discussion! So ...civilized. A warm fire in the wild net. It is *impossible* to force users to be informed. Think about us: We all hang around on this list and missed the information. What would reasonably be expected from a casual user? Often it is not even clear what the consequences are, even if you read the NEWS. "Org now uses electric-indent" only is meaningful to very few people who can guess what that will mean for their workflow. It *seems* impossible to me to be backward compatible forever via code snippets or any other mechanism. You can maybe skip one or two update cycles, but then it will be like pinning a specific git version. One can do that already, but it should not increase the burden of the devels. If those don't have fun anymore, we are lost :-) So we have to live with a breakage from time to time, I guess, but org has very few of those. And it always comes out of these breakages better! Detlef