summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorPatrick Bajao <ebajao@gitlab.com>2020-04-13 10:59:56 +0800
committerPatrick Bajao <ebajao@gitlab.com>2020-04-13 11:00:44 +0800
commitb14b4f39492b5bf3c41232a159fef9bab36c01e4 (patch)
treea752f6113058dc091558d95c98520a724bdbb866 /README.md
parentd274fd4c3b69a751d8b79a15dc75da1cd828eb8b (diff)
downloadgitlab-shell-b14b4f39492b5bf3c41232a159fef9bab36c01e4.tar.gz
Update release steps to be more explicitpb-update-release-steps
Include information about not requiring a second maintainer review when releasing.
Diffstat (limited to 'README.md')
-rw-r--r--README.md10
1 files changed, 6 insertions, 4 deletions
diff --git a/README.md b/README.md
index 7385c12..05c3560 100644
--- a/README.md
+++ b/README.md
@@ -95,10 +95,12 @@ For each version, there is a raw version and a tag version:
To release a new version of GitLab Shell and have that version available to the
Rails application:
-1. Update the [`CHANGELOG`](CHANGELOG) with the **tag version** and the
- [`VERSION`](VERSION) file with the **raw version**.
-2. Add a new git tag with the **tag version**.
-3. Update `GITLAB_SHELL_VERSION` in the Rails application to the **raw
+1. Create a merge request to update the [`CHANGELOG`](CHANGELOG) with the
+ **tag version** and the [`VERSION`](VERSION) file with the **raw version**.
+2. Ask a maintainer to review and merge the merge request. If you're already a
+ maintainer, second maintainer review is not required.
+3. Add a new git tag with the **tag version**.
+4. Update `GITLAB_SHELL_VERSION` in the Rails application to the **raw
version**. (Note: this can be done as a separate MR to that, or in and MR
that will make use of the latest GitLab Shell changes.)