Complete Deprecation and Removal automation to release post
Why is this change being made?
Closes Product#5157 (closed)
- Renames
bin/release-post-deprecations
tobin/release-post-deprecations-removals
- Adds
ReleasePosts::Removals.new.generate
tobin/release-post-deprecations-removals
- Creates
lib/release_posts/removals.rb
to fetch the Removals list from Docs- (unfortunately, the HTML structure is different so
lib/release_posts/deprecations.rb
cannot be shared)
- (unfortunately, the HTML structure is different so
- Adds
deprecations
andremovals
methods tohelpers/release_post_helpers.rb
- Updates the release post template to use those methods to get the deprecations and removals from the
*-index.yml
files for the given milestone - Updates
config[:latest_deprecation_release]
from14.3
to14.0
- (to match where the announcements begin in the Docs)
- Adds a job
.gitlab-ci.yml
- (will depend on a schedule with
RELEASE_POST_DEPRECATIONS_REMOVALS == true
once this MR is approved and merged)
- (will depend on a schedule with
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Brian Rhea