diff options
author | Achilleas Pipinellis <axil@gitlab.com> | 2022-01-21 16:48:05 +0300 |
---|---|---|
committer | Achilleas Pipinellis <axil@gitlab.com> | 2022-01-21 16:48:48 +0300 |
commit | 74c3bc5614783b55940bc18a1085f9abae9d9940 (patch) | |
tree | fc26d70280307d3ed232aea182d1e09d360f1b8a /doc/releases.md | |
parent | c8aefd8c51f6645e340525d6f58445973cbf456b (diff) |
Remove old versions info now that's automated
Diffstat (limited to 'doc/releases.md')
-rw-r--r-- | doc/releases.md | 67 |
1 files changed, 0 insertions, 67 deletions
diff --git a/doc/releases.md b/doc/releases.md index 89fe54db..091f676a 100644 --- a/doc/releases.md +++ b/doc/releases.md @@ -160,73 +160,6 @@ To update `content/_data/versions.yaml` for all online versions (stable branches 1. [Visit the merge requests page](https://gitlab.com/gitlab-org/gitlab-docs/-/merge_requests?label_name%5B%5D=release) to check that their pipelines pass. Set each merge request to _draft_ status and do not merge them yet. -### Update dropdowns for the previous major versions - -The previous major versions are listed under the current versions in the docs: - -![Previous major dropdowns](img/previous_major_dropdowns.png) - -The process to update the dropdowns for the previous major versions is not automated, -so you must create the merge requests manually. -For simplicity, these steps assume you are updating the 13.12 and 12.10 dropdowns. -The steps should be updated when we move to the next major release (15.0). - -1. Create a branch off the stable branch for 13.12. - Use `update-13.12-for-release-<new-version>` for the branch name. For example: - - ```shell - git checkout -b update-13.12-for-release-14.4 origin/13.12 - ``` - -1. Edit `content/_data/versions.yaml` and update the list of versions to reflect the new release: - - - Add the latest version to the `online:` section. - - Remove the oldest version in `online:`. There should now be three - versions in `online:`. - -1. Commit and push. For example, for the 14.4 release: - - ```shell - git add content/_data/versions.yaml - git commit -m "Update dropdown to 14.4" - git push origin update-13.12-for-release-14.4 - ``` - -1. Create the merge request: - - For the target branch, select the previous version's stable branch, in this case, `13.12` (do not select `main`!) - - Add the `~Technical Writing` and `~release` labels. - - Set the merge request to _draft_ status. - - [Example merge request](https://gitlab.com/gitlab-org/gitlab-docs/-/merge_requests/2219) for the 14.4 release. - -1. Create a branch off the stable branch for 12.10. - Use `update-12.10-for-release-<new-version>` for the branch name. For example: - - ```shell - git checkout -b update-12.10-for-release-14.4 origin/12.10 - ``` - -1. Edit `content/_data/versions.yaml` and update the list of versions to reflect the new release: - - - Add the latest version to the `online:` section. - - Remove the oldest **current** version from `online:`. - -1. Commit and push. For example, for the 14.4 release: - - ```shell - git add content/_data/versions.yaml - git commit -m "Update dropdown to 14.4" - git push origin update-12.10-for-release-14.4 - ``` - -1. Create the merge request: - - For the target branch, select the previous version's stable branch, in this case, `12.10` (do not select `main`!) - - Add the `~Technical Writing` and `~release` labels. - - Set the merge request to _draft_ status. - - [Example merge request](https://gitlab.com/gitlab-org/gitlab-docs/-/merge_requests/2220) for the 14.4 release. - -1. [Visit the merge requests page](https://gitlab.com/gitlab-org/gitlab-docs/-/merge_requests?label_name%5B%5D=release) - to check that their pipelines pass. Do not merge them yet. - ## Merge merge requests and run Docker image builds _Do this after the release post is live._ |