From f68003560d96a9c2b9496e9091c809d1e17402e9 Mon Sep 17 00:00:00 2001
From: Jacob Vosmaer <contact@jacobvosmaer.nl>
Date: Fri, 21 Nov 2014 09:59:46 +0100
Subject: [PATCH] The blog post will trigger a mail to the list

---
 doc/release/security.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/doc/release/security.md b/doc/release/security.md
index 79d23c02ea4..d335407797b 100644
--- a/doc/release/security.md
+++ b/doc/release/security.md
@@ -18,7 +18,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/)