diff options
| author | Marin Jankovski <maxlazio@gmail.com> | 2014-12-05 12:34:18 +0100 |
|---|---|---|
| committer | Marin Jankovski <maxlazio@gmail.com> | 2014-12-05 12:34:18 +0100 |
| commit | 90a308ea00ece729b15b430a397d22e3b3fe3102 (patch) | |
| tree | 0f05749945d9f6853c128022f9fc779c7ac6e717 /doc/release/security.md | |
| parent | e6c5a8b161c89a03ca5ee6666f65cf4cfbfa4ab9 (diff) | |
| download | gitlab-ce-90a308ea00ece729b15b430a397d22e3b3fe3102.tar.gz | |
Update release docs to deploy to GitLab.com before publishing.
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 c24a394ef4a..b67e0f37a04 100644 --- a/doc/release/security.md +++ b/doc/release/security.md @@ -17,6 +17,7 @@ Please report suspected security vulnerabilities in private to <support@gitlab.c 1. Inform the release manager that there needs to be a security release 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 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` |