I would try to rephrase the text to talk about operations and usage instead of operators and users. Reasoning behind this is, that especially user is misleading. A user in this sense is in many cases a developer of a tooling that makes use of an api. Referring to the situation as usage could make reading the guide easier to digest.

IT Operations Management is well established ITIL lingo and should be easily understood by the audience of this TRG.

@ClosedSourcerer @lgblaumeiser so you would propose something like "A migration guide should support IT operations management and enable usage of a new release"?

It is not that easy, I have to admit

I really hate the fact, that TRGs are currently not very consistent in their structure.

20 TRGs use Example
5 TRGs Use Best Practice
1 TRG uses Best Practices and Example

I suggest switching to Example and also including an example and scrapping Best Practice

@ClosedSourcerer Examples and Best Practices are two different things for me. I chose not to provide an example, because this always depends on the application... We could however link to "good examples" that already do that, such as the portal or the EDC. I'd still like to keep the best practices... would you suggest to add them to the "description"?

IT Operations Management is well established ITIL lingo and should be easily understood by the audience of this TRG.

We could narrow the need for a migration guide to major releases only, which is the case where breaking changes can occur.

@rafaelmag110 we aren't really following semantic versioning in all products - EDC and DTR contain "breaking breaking changes" although we just increase the minor counter. So a proposal could be "There must be a dedicated migration guide for each major release. For minor releases a guide must only be provided if it affects the usage or operation of a service.