Track breaking changes that need to land in 14.0
NOTE - 14.0 IS SCHEDULED FOR June 22
Presently GitLab is planning to release our next major release on May 22nd:
Per GitLab's Versioning Policy, non-backward compatible and breaking changes are recommended for a major release, whereas backward compatible changes can be introduced in a minor release.
Following the deprecation guidelines:
If the deprecation is scheduled for an upcoming release, the content should remain in the release post until it has been completed. For example, if a deprecation is announced in the 12.9 release post and scheduled to be completed in 13.0, the same content would be included in release posts 12.9, 12.10, and 13.0.
We should be announcing deprecations in %13.9.
Please be mindful of any planned deprecation, removal and upgrade of any feature.
In the spreadsheet linked below, please add any planned deprecations, and make sure to announce them in all the upcoming milestones until (and including 14.0) and mark any breaking change
The definition for a breaking change is: As a GitLab.com user, if I do not take any action - something will break in my workflow. This includes corner cases and does not include removing something that has already been deprecation.