diff options
| author | Marin Jankovski <maxlazio@gmail.com> | 2015-03-11 21:11:32 -0700 |
|---|---|---|
| committer | Marin Jankovski <maxlazio@gmail.com> | 2015-03-11 21:11:32 -0700 |
| commit | 3f823068e1f6e3e88d6631de60d9aaf9ecd5e6f9 (patch) | |
| tree | 543a78280f3c3a50586dbd24fc99c0faa64c4a9e /doc/release/security.md | |
| parent | f29a7ce51f1f9d859258e190cf1d01c3d58806e1 (diff) | |
| download | gitlab-ce-3f823068e1f6e3e88d6631de60d9aaf9ecd5e6f9.tar.gz | |
Add deploy to ci.gitlab.com to release documents.
Diffstat (limited to 'doc/release/security.md')
| -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 6ed25264498..60bcfbb6da5 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. Build the package for ci.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 |