...

We need very good reasons to make changes that break compatibility in those areas, along with "bridges" to avoid breaking older code and systems.

A reasonable way to avoid such problems might be to create a "glossary of recommended terms" used for new code and in places where changes have no unwanted impact. And clearly explain in that document why we are not changing existing code in places where that would break backwards compatibility.

Topics

Rename 'master' Git branch

...