summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSean McGivern <sean@gitlab.com>2017-03-29 17:00:17 +0100
committerSean McGivern <sean@gitlab.com>2017-03-29 17:00:17 +0100
commitf618d47964acc03af8c4e9f9c0295db4a95eed77 (patch)
tree550dccbd292278f672de323d2f0736bb8eef2862
parent199e2d62ebea9939e48d442c6a866d26d0aede4f (diff)
downloadgitlab-shell-f618d47964acc03af8c4e9f9c0295db4a95eed77.tar.gz
Explain how to release a new version
-rw-r--r--README.md14
1 files changed, 14 insertions, 0 deletions
diff --git a/README.md b/README.md
index 8ba6b3b..dba278e 100644
--- a/README.md
+++ b/README.md
@@ -131,3 +131,17 @@ Remove all keys from authorized_keys file:
## Git LFS remark
Starting with GitLab 8.12, GitLab supports Git LFS authentication through ssh.
+
+## Releasing a new version
+
+GitLab Shell is versioned by git tags, and the version used by the Rails
+application is stored in
+[`GITLAB_SHELL_VERSION`](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/GITLAB_SHELL_VERSION).
+To release a new version of GitLab Shell and have that version available to the
+Rails application:
+
+1. Update the [`CHANGELOG`](CHANGELOG) and [`VERSION`](VERSION) files.
+2. Add a new git tag.
+3. Update `GITLAB_SHELL_VERSION` in the Rails application. (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.)