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: The blog post will trigger a mail to the list

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

(limited to 'doc/release/security.md')

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/)
-- 
cgit v1.2.1


From 4e3bf439cba782bf7d3ea326f0f6f5878166f0e2 Mon Sep 17 00:00:00 2001
From: Jacob Vosmaer <contact@jacobvosmaer.nl>
Date: Mon, 24 Nov 2014 12:14:19 +0100
Subject: Establish ownership of security releases

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

(limited to 'doc/release/security.md')

diff --git a/doc/release/security.md b/doc/release/security.md
index 79d23c02ea4..a7fb57921df 100644
--- a/doc/release/security.md
+++ b/doc/release/security.md
@@ -14,7 +14,9 @@ Please report suspected security vulnerabilities in private to <support@gitlab.c
 
 1. Verify that the issue can be reproduced
 1. Acknowledge the issue to the researcher that disclosed it
+1. Inform the release manager that there needs to be a security release
 1. Do the steps from [patch release document](doc/release/patch.md), starting with "Create an issue on private GitLab development server"
+1. The MR with the security fix should get a 'security' label and be assigned to the release manager
 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`
-- 
cgit v1.2.1


From 90a308ea00ece729b15b430a397d22e3b3fe3102 Mon Sep 17 00:00:00 2001
From: Marin Jankovski <maxlazio@gmail.com>
Date: Fri, 5 Dec 2014 12:34:18 +0100
Subject: Update release docs to deploy to GitLab.com before publishing.

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

(limited to 'doc/release/security.md')

diff --git a/doc/release/security.md b/doc/release/security.md
index c24a394ef4a..b67e0f37a04 100644
--- a/doc/release/security.md
+++ b/doc/release/security.md
@@ -17,6 +17,7 @@ Please report suspected security vulnerabilities in private to <support@gitlab.c
 1. Inform the release manager that there needs to be a security release
 1. Do the steps from [patch release document](doc/release/patch.md), starting with "Create an issue on private GitLab development server"
 1. The MR with the security fix should get a 'security' label and be assigned to the release manager
+1. Build the package for GitLab.com and do a deploy
 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`
-- 
cgit v1.2.1