Skip to content

Add a migrations section to the release post

Brian Rhea requested to merge add-migrations-section-to-release-post into master

Why is this change being made?

This MR only contains initial changes to test the structure of migrations content.

If this proposal is approved, the following changes need to be added to this MR:

  • Update handbook to include information about adding migrations to the release post
  • Update the release post merge request template and/or the kickoff automation as necessary

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.
  • 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
  • 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

Merge request reports

Loading