[Meta] Deprecations Plan

[TinaHeiligers]

Plan outline for major version upgrade

We need to prepare for breaking changes planned for the next major stack version upgrade, taking into account larger discussions needed for handling deprecations based on offering type.

As most, if not all teams depend on core APIs and services, priority is on Core followed by rolling out the plan to other teams.

TODO:

• Compile a list of existing deprecations/changes we want to make (current and left over from previous upgrade)
• Frame justifications for the breaking changes committee, accounting for different offerings
• Re-audit list of approved changes
• Handle approved breaking changes

[TinaHeiligers]

Frame justifications for the breaking changes committee, accounting for different offerings

Our serverless offering does not allow breaking changes and we need to decide on a migration plan for each deprecation.

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)