Skip to content

Add Secure release process documentation

Lucas Charles requested to merge migrate-secure-release-process-doc-to-team-page into master

Why is this change being made?

Port the outdated Release process docs to the handbook. This makes the single-source-of-truth a bit clearer and reduces the number of disparate projects containing documentation. The old docs were also heavily outdated, so this MR updates accordingly.

We should probably port over the QA process too but let's iterate 👣

Review app: https://migrate-secure-release-process-doc-to-team-page.about.gitlab-review.app/handbook/engineering/development/secure/release_process.html

EM checklist

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

Edited by Olivier Gonzalez

Merge request reports