From a216fa7ea3229fcd386f53c89f2079b6bf5f59a7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Matthias=20K=C3=A4ppler?= <mkaeppler@gitlab.com>
Date: Thu, 5 Nov 2020 07:53:51 +0000
Subject: [PATCH] Update release steps
Now mentions that the gitlab repo also needs to be updated
for the version to be deployed to .com.
---
PROCESS.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/PROCESS.md b/PROCESS.md
index 452f7e93946e7..07f553dd38796 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -39,6 +39,9 @@ maintainers. The release process is:
- run `make tag VERSION=x.y.z"` or `make signed_tag VERSION=x.y.z` on the release branch. This will
compile the changelog, bump the VERSION file, and make a tag matching it.
- push the branch and the tag to gitlab.com
+- the new version will only be deployed to `gitlab.com` if [`GITLAB_WORKHORSE_VERSION`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/GITLAB_WORKHORSE_VERSION) is updated accordingly;
+ if applicable, please remind the person who originally asked for a new release to make this change
+ (the MR should include a link back to the [version tag](https://gitlab.com/gitlab-org/gitlab-workhorse/-/tags) and a copy of the changelog)
## Security releases
--
GitLab