Skip to content

dev escalation support for the Release Post process

Chase Southard requested to merge release_post_escalation_scope into master

Why is this change being made?

Recent challenges with the Release Post process have brought to light the need for regular developer support during crucial phases of the Release Post process namely assembly and deployment. This addition to the dev escalation process defines the blockers to the Release Post process as a fully qualified emergency requiring engineering support.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct 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 in 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 relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)
Edited by Chase Southard

Merge request reports