diff options
| author | Jacob Vosmaer <contact@jacobvosmaer.nl> | 2014-11-24 12:14:19 +0100 |
|---|---|---|
| committer | Jacob Vosmaer <contact@jacobvosmaer.nl> | 2014-11-24 12:14:19 +0100 |
| commit | 4e3bf439cba782bf7d3ea326f0f6f5878166f0e2 (patch) | |
| tree | 6cd937ddddf73d5d640d6a16982523c8ee9aa4b3 /doc/release/security.md | |
| parent | e0c870c0451789318e46ff5cb2b44a8d7d555f4c (diff) | |
| download | gitlab-ce-4e3bf439cba782bf7d3ea326f0f6f5878166f0e2.tar.gz | |
Establish ownership of security releases
Diffstat (limited to 'doc/release/security.md')
| -rw-r--r-- | doc/release/security.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/release/security.md b/doc/release/security.md index 79d23c02ea4..a7fb57921df 100644 --- a/doc/release/security.md +++ b/doc/release/security.md @@ -14,7 +14,9 @@ Please report suspected security vulnerabilities in private to <support@gitlab.c 1. Verify that the issue can be reproduced 1. Acknowledge the issue to the researcher that disclosed it +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. 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` |