[DOC] Guides - Troubleshooting: Add Breaking Changes Page

[thabaum]

Seems like there are versions that "break" developer modules. I would like us to post these here in basic form so we can investigate them further and document them in a "breaking-changes.md" file if that sounds right?

I would think this would get produced with release notes each release. But it would be nice to have a reference to each time something happens and what to do if nothing else a link to an issue created that has the solution.

[INNO-Software]

We definitely want to channel issues into tracked bugs, and even do special messaging around possibly widespread issues caused by a new release. That being said, I think we shouldn't call unplanned issues "breaking-changes" because the industry often only associates that with planned breaking changes. e.g. The removal of Telerik from a CMS, might break ALL vendors relying on it.

Meaning, these usually become associated to builds, where vendors can learn when they will have to sunset (or replace) components broken by roadmap updates. Or for a client to know which updates might break a 3rd party module they rely upon.

Just as with the 'What's New?' messaging, they are often best stored closely with builds themselves as 'release notes' tend to be. Primarily as they are so build specific, and their value is always associated with choose, or moving between, product builds.