Fetch deprecations and removals from `gitlab-org/gitlab`
Problem
Each milestone, we manually create a .yml
file on the 19th with the deprecations for that release by referencing our Deprecations page. This file is compiled into the release post and displayed in the "Deprecations" section.
This is susceptible to human error because if a deprecation is merged after the due date of the 18th that we communicate to the product team, it will not be included unless steps are taken outside of the established process.
Example
Solution
In support of our direction toward automating the release post, one step we can take is automating the creation of a deprecation index so that the release post simply pulls the list for the matching release from that file.
This will remove manual steps from the process and ensure an up-to-date list of deprecations and removal announcements in the release post.
Implementation
-
Automate deprecation index creation www-gitlab-com!116841 (merged) -
Automate removal index creation www-gitlab-com!119416 (merged) -
Update the release post template to pull from above .yml
files instead of the current structure www-gitlab-com!119416 (merged) -
Add above scripts to the pipeline schedule www-gitlab-com!119416 (merged)