diff options
| author | Patricio Cano <patricio@gitlab.com> | 2014-12-23 17:28:09 -0500 |
|---|---|---|
| committer | Patricio Cano <patricio@gitlab.com> | 2014-12-23 17:28:09 -0500 |
| commit | 4386c210a17e071822126bccfedf0e19fbf1eb0a (patch) | |
| tree | b571b7f92c452d5bea18ce252ca9878be2348586 /doc/release | |
| parent | ad85f1ea78bc7d58db2e11fc47e9d02ac5f4d3d2 (diff) | |
| download | gitlab-ce-4386c210a17e071822126bccfedf0e19fbf1eb0a.tar.gz | |
Updated the monthly release steps
Diffstat (limited to 'doc/release')
| -rw-r--r-- | doc/release/monthly.md | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/doc/release/monthly.md b/doc/release/monthly.md index ea7865b4b2b..b31fd885404 100644 --- a/doc/release/monthly.md +++ b/doc/release/monthly.md @@ -200,7 +200,7 @@ Add to your local `gitlab-ci/.git/config`: # **4 workdays before release - Release RC1** -### **1. Determine QA person +### **1. Determine QA person** Notify person of QA day. @@ -215,6 +215,7 @@ It is important to do this as soon as possible, so we can catch any errors befor ### **3. Prepare the blog post** - Start with a complete copy of the [release blog template](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/doc/release_blog_template.md) and fill it out. +- Make sure the blog post contains information about the GitLab CI release. - Check the changelog of CE and EE for important changes. - Also check the CI changelog - Add a proposed tweet text to the blog post WIP MR description. @@ -269,7 +270,7 @@ Create an issue with description of a problem, if it is quick fix fix it yoursel **NOTE** If there is a problem that cannot be fixed in a timely manner, reverting the feature is an option! If the feature is reverted, create an issue about it in order to discuss the next steps after the release. -# **22nd - Release CE, EE and CI** +# **Workday before release - Create Omnibus tags and build packages** **Make sure EE `x-x-stable-ee` has latest changes from CE `x-x-stable`** @@ -306,15 +307,17 @@ Follow the [release doc in the Omnibus repository](https://gitlab.com/gitlab-org This can happen before tagging because Omnibus uses tags in its own repo and SHA1's to refer to the GitLab codebase. -### **4. Publish packages for new release** +# **22nd - Release CE, EE and CI** + +### **1. Publish packages for new release** Update `downloads/index.html` and `downloads/archive/index.html` in `www-gitlab-com` repository. -### **5. Publish blog for new release** +### **2. Publish blog for new release** Merge the [blog merge request](#1-prepare-the-blog-post) in `www-gitlab-com` repository. -### **6. Tweet to blog** +### **3. Tweet to blog** Send out a tweet to share the good news with the world. List the most important features and link to the blog post. |