Skip to content

Emergency change process for GitLab SaaS

Marin Jankovski requested to merge mj/emergency-change-process into master

Why is this change being made?

We have an emergency protocol for rolling out changes to GitLab SaaS in each individual process, but we have no single page that gives a high level overview. This topic is coming up more frequently in discussions with Compliance, so adding this single page as a means to consolidate and be more explicit.

Fixes https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/10557

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

For help with failing pipelines reach out in #mr-buddies in Slack

Merge request reports