From 47b5b3d5fad0bf9a0193e8d01e6c4d9656583a45 Mon Sep 17 00:00:00 2001 From: Sytse Sijbrandij Date: Fri, 22 Aug 2014 21:46:12 +0200 Subject: Tar before omnibus build, we all have master access on dev, don't forget to update installation.md --- doc/release/monthly.md | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/doc/release/monthly.md b/doc/release/monthly.md index 09bdde81dcc..e40fbbef70c 100644 --- a/doc/release/monthly.md +++ b/doc/release/monthly.md @@ -221,12 +221,7 @@ git checkout -b x-x-stable git push x-x-stable ``` -### **2. Build the Omnibus packages** - -Follow the [release doc in the Omnibus repository](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/release.md). -This can happen before tagging because Omnibus uses tags in its own repo and SHA1's to refer to the GitLab codebase. - -### **3. Set VERSION to x.x.x and push** +### **2. Set VERSION to x.x.x and push** Change the GITLAB_SHELL_VERSION file in `master` of the CE repository if the version changed. @@ -236,7 +231,7 @@ Change the VERSION file in `master` branch of the CE repository and commit. Cher Change the VERSION file in `master` branch of the EE repository and commit. Cherry-pick into the `x-x-stable-ee` branch of EE. -### **4. Create annotated tag vx.x.x** +### **3. Create annotated tag vx.x.x** In `x-x-stable` branch check for the SHA-1 of the commit with VERSION file changed. Tag that commit, @@ -246,12 +241,17 @@ git tag -a vx.x.0 -m 'Version x.x.0' xxxxx where `xxxxx` is SHA-1. -### **5. Push the tag** +### **4. Push the tag** ``` git push origin vx.x.0 ``` +### **5. Build the Omnibus packages** + +Follow the [release doc in the Omnibus repository](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/release.md). +This can happen before tagging because Omnibus uses tags in its own repo and SHA1's to refer to the GitLab codebase. + ### **6. Push to remotes** For GitLab CE, push to dev, GitLab.com and GitHub. @@ -260,8 +260,6 @@ For GitLab EE, push to the subscribers repo. Make sure the branch is marked 'protected' on each of the remotes you pushed to. -NOTE: You might not have the rights to push to master on dev. Ask Dmitriy. - ### **7. Publish blog for new release** Merge the [blog merge request](#1-prepare-the-blog-post) in `www-gitlab-com` repository. @@ -282,6 +280,10 @@ Include a link to the blog post and keep it short. Proposed email text: "We have released a new version of GitLab. See our blog post() for more information." +### **10. Update installation.md** + +Update [installation.md](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md) to the newest version. + # **23rd - Optional Patch Release** # **24th - Update GitLab.com** -- cgit v1.2.1 From 18ec2f93a6c8a1cb783af1522f198668481d2384 Mon Sep 17 00:00:00 2001 From: Sytse Sijbrandij Date: Fri, 22 Aug 2014 21:49:39 +0200 Subject: Don't forget to cherry pick into stable. --- doc/release/monthly.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/release/monthly.md b/doc/release/monthly.md index e40fbbef70c..dfde53fe3a0 100644 --- a/doc/release/monthly.md +++ b/doc/release/monthly.md @@ -282,7 +282,7 @@ Proposed email text: ### **10. Update installation.md** -Update [installation.md](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md) to the newest version. +Update [installation.md](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md) to the newest version in master and cherry-pick that commit into the stable branch. # **23rd - Optional Patch Release** -- cgit v1.2.1