summaryrefslogtreecommitdiff
path: root/doc/release/security.md
diff options
context:
space:
mode:
authorSytse Sijbrandij <sytses@gmail.com>2014-07-21 10:50:03 +0200
committerSytse Sijbrandij <sytses@gmail.com>2014-07-21 10:50:03 +0200
commitebc1c4bde95abaa7f362faea4c1b5f58d29fa45a (patch)
treee9282a5acb876146d0f4694223918a9d3cede9c3 /doc/release/security.md
parente443e59542911e21684abdc1493bb041ec179a4f (diff)
downloadgitlab-ce-ebc1c4bde95abaa7f362faea4c1b5f58d29fa45a.tar.gz
Account for the EE only situation.
Diffstat (limited to 'doc/release/security.md')
-rw-r--r--doc/release/security.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/release/security.md b/doc/release/security.md
index 3944f55e03f..f20d7e16222 100644
--- a/doc/release/security.md
+++ b/doc/release/security.md
@@ -18,7 +18,7 @@ Please report suspected security vulnerabilities in private to <support@gitlab.c
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`
-1. Send out an email to the 'GitLab Newsletter' mailing list on MailChimp
+1. Send out an email to the 'GitLab Newsletter' mailing list on MailChimp (or the 'Subscribers' list if the security fix is for EE only)
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
1. Add the security researcher to the [Security Researcher Acknowledgments list](http://www.gitlab.com/vulnerability-acknowledgements/)