summaryrefslogtreecommitdiff
path: root/doc/release/patch.md
diff options
context:
space:
mode:
authorMarin Jankovski <maxlazio@gmail.com>2015-03-11 21:11:32 -0700
committerMarin Jankovski <maxlazio@gmail.com>2015-03-11 21:11:32 -0700
commit3f823068e1f6e3e88d6631de60d9aaf9ecd5e6f9 (patch)
tree543a78280f3c3a50586dbd24fc99c0faa64c4a9e /doc/release/patch.md
parentf29a7ce51f1f9d859258e190cf1d01c3d58806e1 (diff)
downloadgitlab-ce-3f823068e1f6e3e88d6631de60d9aaf9ecd5e6f9.tar.gz
Add deploy to ci.gitlab.com to release documents.
Diffstat (limited to 'doc/release/patch.md')
-rw-r--r--doc/release/patch.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/release/patch.md b/doc/release/patch.md
index 5397343e715..68156ae9c0e 100644
--- a/doc/release/patch.md
+++ b/doc/release/patch.md
@@ -51,6 +51,7 @@ CE=false be rake release['x.x.x']
1. [Build new packages with the latest version](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/release.md)
1. Apply the patch to GitLab.com and the private GitLab development server
+1. Apply the patch to ci.gitLab.com and the private GitLab CI development server
1. Create and publish a blog post, see [patch release blog template](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/doc/patch_release_blog_template.md)
1. Send tweets about the release from `@gitlab`, tweet should include the most important feature that the release is addressing and link to the blog post
1. Note in the 'GitLab X.X regressions' issue that the patch was published (CE only)