Draft: Minimize impact of breaking changes
What does this MR do and why?
- Provides handbook references to minimize breaking changes where possible by measuring usage and building tooling for users
- Add the same list to the
Deprecations.md
SSOT issue so that each breaking change is reviewed to minimize impact - Adds Engineering as DRIs to development efforts
- Requires EM, SEM/Director and GMP/Director to approve the Deprecations issue checklist (as there is a plan for managing the breaking change)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Edited by Cheryl Li