diff options
| author | Hank Taylor <hank@gitlab.com> | 2016-03-18 06:31:29 +0000 |
|---|---|---|
| committer | Hank Taylor <hank@gitlab.com> | 2016-03-18 06:31:29 +0000 |
| commit | 3f72d0aee546a39d67c684c360a861e28080a4a9 (patch) | |
| tree | faef951b778692134b4226b8d9f747f855f01530 | |
| parent | fc75de7dc2c90deb0dccede8a42ada8cc4792678 (diff) | |
| download | gitlab-ce-notify_marketing.tar.gz | |
added item to notify marketing of security releasesnotify_marketing
| -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 b1a62b333e6..9ca0057c2cd 100644 --- a/doc/release/security.md +++ b/doc/release/security.md @@ -22,6 +22,7 @@ Please report suspected security vulnerabilities in private to <support@gitlab.c 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. Notify Marketing via chat so they can email members of the security mailing list 1. Send tweets about the release from `@gitlabhq` 1. Send out an email to [the community google mailing list](https://groups.google.com/forum/#!forum/gitlabhq) 1. Post a signed copy of our complete announcement to [oss-security](http://www.openwall.com/lists/oss-security/) and request a CVE number. CVE is only needed for bugs that allow someone to own the server (Remote Code Execution) or access to code of projects they are not a member of. |