summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJob van der Voort <jobvandervoort@gmail.com>2015-03-11 17:31:39 +0100
committerJob van der Voort <jobvandervoort@gmail.com>2015-03-11 17:31:39 +0100
commit536d4373737cf5c4710d949fb4819d99faf2cdd7 (patch)
tree1d289098f400be8ff249c623550538c9a34aa489 /doc
parentc621a7712b7f75e0a71224c15983e68fd465d69b (diff)
downloadgitlab-ce-536d4373737cf5c4710d949fb4819d99faf2cdd7.tar.gz
add AMI update step
Diffstat (limited to 'doc')
-rw-r--r--doc/release/monthly.md4
-rw-r--r--doc/release/patch.md1
2 files changed, 5 insertions, 0 deletions
diff --git a/doc/release/monthly.md b/doc/release/monthly.md
index dd44c1eb860..a7e5faf2a6e 100644
--- a/doc/release/monthly.md
+++ b/doc/release/monthly.md
@@ -200,3 +200,7 @@ Consider creating a post on Hacker News.
## Update GitLab.com with the stable version
- Deploy the package (should not need downtime because of the small difference with RC1)
+
+## Release new AMIs
+
+[Follow this guide](https://dev.gitlab.org/gitlab/AMI/blob/master/README.md)
diff --git a/doc/release/patch.md b/doc/release/patch.md
index 80afa19b6c5..5397343e715 100644
--- a/doc/release/patch.md
+++ b/doc/release/patch.md
@@ -54,3 +54,4 @@ CE=false be rake release['x.x.x']
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)
+1. [Create new AMIs](https://dev.gitlab.org/gitlab/AMI/blob/master/README.md)