summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorValery Sizov <valery@gitlab.com>2014-10-21 12:04:09 +0300
committerValery Sizov <valery@gitlab.com>2014-10-21 12:04:09 +0300
commit6c476a8dac8411f9a9d5a2cbf9ff088dc55369d9 (patch)
treeb078e8d7f10b59a09caa459c7e52c00561d0146d
parentc3b81e5f400ebc935683fc2cf0e561b2b17a1052 (diff)
downloadgitlab-ce-6c476a8dac8411f9a9d5a2cbf9ff088dc55369d9.tar.gz
Improved release documentation
-rw-r--r--doc/release/monthly.md8
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/release/monthly.md b/doc/release/monthly.md
index c46a3ed9c93..f972fd20364 100644
--- a/doc/release/monthly.md
+++ b/doc/release/monthly.md
@@ -11,7 +11,7 @@ NOTE: This is a guide for GitLab developers.
A release manager is selected that coordinates the entire release of this version. The release manager has to make sure all the steps below are done and delegated where necessary. This person should also make sure this document is kept up to date and issues are created and updated.
### **3. Create an overall issue**
-Name it "Release x.x.x" for easier searching.
+Create issue for GitLab CE project(internal). Name it "Release x.x.x" for easier searching.
```
15th:
@@ -156,6 +156,12 @@ Create an annotated tag that points to the version change commit:
git tag -a vx.x.0.rc1 -m 'Version x.x.0.rc1'
```
+Tags should be created for both GitLab CE and GitLab EE. Don't forget to push tags to all remotes.
+
+```
+git push remote_name vx.x.0.rc1
+```
+
### **6. Create stable branches**
For GitLab EE, append `-ee` to the branch.