diff options
| author | Marin Jankovski <maxlazio@gmail.com> | 2015-03-11 17:50:02 -0700 |
|---|---|---|
| committer | Marin Jankovski <maxlazio@gmail.com> | 2015-03-11 17:50:02 -0700 |
| commit | 66384d7d4434f9185dbe8bfe22cb7db974763ed3 (patch) | |
| tree | 2c74d009497959620b8e21dbb90d0f42b00c892f /doc/release | |
| parent | 536d4373737cf5c4710d949fb4819d99faf2cdd7 (diff) | |
| download | gitlab-ce-66384d7d4434f9185dbe8bfe22cb7db974763ed3.tar.gz | |
Add a note about building AMI to security doc
Diffstat (limited to 'doc/release')
| -rw-r--r-- | doc/release/security.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/release/security.md b/doc/release/security.md index 1575fcf2708..6ed25264498 100644 --- a/doc/release/security.md +++ b/doc/release/security.md @@ -18,6 +18,7 @@ Please report suspected security vulnerabilities in private to <support@gitlab.c 1. Do the steps from [patch release document](doc/release/patch.md), starting with "Create an issue on private GitLab development server" 1. The MR with the security fix should get a 'security' label and be assigned to the release manager 1. Build the package for GitLab.com and do a deploy +1. [Create new AMIs](https://dev.gitlab.org/gitlab/AMI/blob/master/README.md) 1. Create feature branches for the blog post on GitLab.com and link them from the code branch 1. Merge and publish the blog posts 1. Send tweets about the release from `@gitlabhq` |