Skip to content

Update RPM MR template following 17.7 retro

Courtney Meddaughrequested to merge
courtmeddaugh-master-patch-020a into master

Why is this change being made?

Making updates to the Release Post MR template per feedback captured in the Release Post 17.7 Retrospective (#35059 - closed) (I was RPM for %17.7 - these are mostly areas that caused me a bit of confusion or I thought could use some clarification).

Changes included:

  1. Clarifying that breaking changes and removals: Deprecations should be the items listed as Announced in GitLab X.X in the docs, Removals are listed as Removal in GitLab X.X
  2. Clarifying that other links that are expected to be broken on ReviewApp page
  3. Clarifying that that DAY should be tomorrow (Weds of release week) in message to Product Leaders
  4. Clarifying how to get count of features (what exactly to add up) and update the example to be a higher number (changed to 210+) instead of 40+

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • 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
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Commits

  • Update RPM MR template following 17.7 retro
Edited by Courtney Meddaugh

Merge request reports