From 3f72d0aee546a39d67c684c360a861e28080a4a9 Mon Sep 17 00:00:00 2001
From: Hank Taylor <hank@gitlab.com>
Date: Fri, 18 Mar 2016 06:31:29 +0000
Subject: [PATCH] added item to notify marketing of security releases

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

diff --git a/doc/release/security.md b/doc/release/security.md
index b1a62b333e64..9ca0057c2cd6 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.
-- 
GitLab