**TL;DR** There are over `80 deprecations` targeting removal in `17.0` . Some of these deprecations do not have context about the impact or migration paths to alternative functionality. We must assess the impact of these deprecations and identify high/critical impact removals so they can be proactively communicated for customers. ## Context - **Major Release Date: 2024-05-16** - **Cutoff for all deprecation announcements: 2024-02-14** - [GitLab Releases Page](https://about.gitlab.com/releases/) - [17.0 Deprecation Assessment](https://docs.google.com/spreadsheets/d/1bVX943N0GbOSjBOdSzXg_y0aVJyoWPwjCsyBEet-bag/edit#gid=865411820) GitLab's major release date is coming up on `2024-05-16`. All deprecations must be announced prior to the release of `16.9` by `2024-02-14` in order to meet our [deprecations policy](https://handbook.gitlab.com/handbook/product/gitlab-the-product/#deprecations-removals-and-breaking-changes) mandating a gap of 3 minor versions between the announcement of a deprecation and the removal of the feature/functionality. At he time of writing (`2024-02-02`) there are `83` deprecations that customers must manage through. We do not currently have a comprehensive picture of the impact of tall of those deprecations. During the month of February, we should confirm the impact of all deprecations so that we can prepare customer communications and advance notice. ## Specific Asks for PMs If you are unsure of any of the following criteria, please reach out to a CS or Support counterpart who will be able to assist with impact analysis 1. Please Navigate to the [17.0 Deprecation Assessment](https://docs.google.com/spreadsheets/d/1bVX943N0GbOSjBOdSzXg_y0aVJyoWPwjCsyBEet-bag/edit#gid=865411820) spreadsheet 1. Update and/or Verify the following columns for any deprecations in your stage/category with the correct information 1. Impact 1. Impact Scope 1. Impact Assessment 1. Manual Task 1. Impacted Feature 1. Resolution Persona 1. Reporter 1. If your deprecation/removal is high impact, please add a comment to this issue and https://gitlab.com/gitlab-com/customer-success/csm/-/issues/971+ so we can track it as needing customer announcement. In the comment, please include: 1. A Link to the MR that deploys the removal to gitlab.com 2. A link to the deprecation issue 1. Finally, add a comment to this issue confirming that you have completed the steps ## Next Steps - [x] Create List of deprecations along with impact assessment and migration notes. Draft version with initial assessment by CS can be found [here](https://docs.google.com/spreadsheets/d/1bVX943N0GbOSjBOdSzXg_y0aVJyoWPwjCsyBEet-bag/edit#gid=865411820). - [x] Finish additional fields template MR - https://gitlab.com/gitlab-org/gitlab/-/merge_requests/141995+ - [x] Update Deprecation notice with Impact and new required fields - [ ] https://gitlab.com/gitlab-com/customer-success/csm/-/issues/971+ - [ ] Send out Customer Communications - [ ] Email - [ ] Newsletter - [ ] BlogPost ## Exit Criteria - [ ] Publicly available list of high impact breaking changes available - [ ] External customer comms sent