Commit 536d4373 authored by Job van der Voort's avatar Job van der Voort

add AMI update step

parent c621a771
...@@ -200,3 +200,7 @@ Consider creating a post on Hacker News. ...@@ -200,3 +200,7 @@ Consider creating a post on Hacker News.
## Update GitLab.com with the stable version ## Update GitLab.com with the stable version
- Deploy the package (should not need downtime because of the small difference with RC1) - 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)
...@@ -54,3 +54,4 @@ CE=false be rake release['x.x.x'] ...@@ -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. 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. 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. 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)
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment