Skip to content

Move docs project release details

Marcel Amirault requested to merge move-docs-release-out-of-handbook into master

Why is this change being made?

As mentioned in !88489 (comment 653443397) when we first split these docs into their own page in the handbook, this information is better placed directly in the gitlab-docs project.

I feel the addition of really useful troubleshooting information in !90577 (comment 688809788) makes it extra clear that these docs should be in gitlab-docs.

See additional details in the related MR adding the docs to the docs project. This MR is dependent on that one being merged first:

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
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
  • Assign reviewers for this change to the correct DRI(s)
    • 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 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 Marcel Amirault

Merge request reports