diff options
| author | Evan Read <eread@gitlab.com> | 2022-06-27 08:42:58 +0300 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2022-06-28 04:24:39 +0300 |
| commit | c37ebc57c636879d6d6b0c540394b1dc28c194be (patch) | |
| tree | 7497a6492428b5737a252886fe4016424bd89c02 /doc | |
| parent | 40cc22d12e91830a0d8d14d08db9aba475f9ee72 (diff) | |
Refine docs release template and update release documentationeread/refine-docs-release-template
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/releases.md | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/releases.md b/doc/releases.md index d2ad4066..962118f6 100644 --- a/doc/releases.md +++ b/doc/releases.md @@ -37,6 +37,9 @@ To minimize problems during the documentation release process, use the following - Complete the preparation steps between the 17th and the 20th of the month. **All** of the following steps must be completed successfully before proceeding with the publication steps: + 1. If an issue was not already created for you by the TW that handled the last release, + [create an issue for the release](https://gitlab.com/gitlab-org/gitlab-docs/-/issues/new?issuable_template=release) + to track your progress and ensure completeness. 1. [Create a stable branch and Docker image](#create-stable-branch-and-docker-image-for-release) for the new version. 1. [Create a release merge request](#create-release-merge-request) for the new version, which @@ -186,9 +189,9 @@ The merge requests for the dropdowns should now all be merged into their respect 1. Merge all of the [dropdown merge requests](#update-dropdown-for-online-versions). 1. Merge the [release merge request](#create-release-merge-request). 1. Each merge triggers a new pipeline for each stable branch. - Check the [pipelines page](https://gitlab.com/gitlab-org/gitlab-docs/pipelines) and wait + Check the [pipelines page](https://gitlab.com/gitlab-org/gitlab-docs/-/pipelines) and wait for all the stable branch pipelines to complete. -1. Go to the [scheduled pipelines page](https://gitlab.com/gitlab-org/gitlab-docs/pipeline_schedules) +1. Go to the [scheduled pipelines page](https://gitlab.com/gitlab-org/gitlab-docs/-/pipeline_schedules) and run the `Build docker images weekly` pipeline. 1. In the scheduled pipeline you just started, manually run the **image:docs-latest** job that builds the `:latest` Docker image. 1. When the pipeline is complete, run the `Build docs.gitlab.com every 4 hours` scheduled pipeline to deploy all new versions to the public documentation site. |