diff options
| author | Sytse Sijbrandij <sytse@gitlab.com> | 2014-12-01 09:52:10 +0000 |
|---|---|---|
| committer | Sytse Sijbrandij <sytse@gitlab.com> | 2014-12-01 09:52:10 +0000 |
| commit | 30e28a7e0c458395b7a205e72a89e7d1b68571eb (patch) | |
| tree | 4cb46bb0d55b778c5ace98a6f42c0ca79d1548ba | |
| parent | 3dc986cff191a3db60d07b9a841275062b5eb3fa (diff) | |
| parent | f68003560d96a9c2b9496e9091c809d1e17402e9 (diff) | |
| download | gitlab-ce-30e28a7e0c458395b7a205e72a89e7d1b68571eb.tar.gz | |
Merge branch 'security-release' into 'master'
Improve security release documentation
I think the MailChimp step is not needed anymore because we automated it.
See merge request !1271
| -rw-r--r-- | doc/release/security.md | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/doc/release/security.md b/doc/release/security.md index a7fb57921df..c24a394ef4a 100644 --- a/doc/release/security.md +++ b/doc/release/security.md @@ -20,7 +20,6 @@ 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 (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://about.gitlab.com/vulnerability-acknowledgements/) |