diff options
| author | Sytse Sijbrandij <sytses@gmail.com> | 2014-07-21 10:47:38 +0200 |
|---|---|---|
| committer | Sytse Sijbrandij <sytses@gmail.com> | 2014-07-21 10:47:38 +0200 |
| commit | e443e59542911e21684abdc1493bb041ec179a4f (patch) | |
| tree | 5e43a456df3c185d2dd24cf97f9568faef935006 | |
| parent | 6a10e2e52a1ae614fe467245e5e5946e67e0905d (diff) | |
| download | gitlab-ce-e443e59542911e21684abdc1493bb041ec179a4f.tar.gz | |
Simplify email procedure now that subscribers are on the newsletter list.
| -rw-r--r-- | doc/release/monthly.md | 9 | ||||
| -rw-r--r-- | doc/release/patch.md | 3 | ||||
| -rw-r--r-- | doc/release/security.md | 3 |
3 files changed, 8 insertions, 7 deletions
diff --git a/doc/release/monthly.md b/doc/release/monthly.md index f37b5720c39..1d60eb33b02 100644 --- a/doc/release/monthly.md +++ b/doc/release/monthly.md @@ -262,13 +262,14 @@ Proposed tweet for CE "GitLab X.X.X CE is released! It brings *** <link-to-blogp Proposed tweet for EE "GitLab X.X.X EE is released! It brings *** <link-to-blogpost>" -### **9. Send out newsletter** - -In MailChimp replicate the former release newsletters to customers / newsletter subscribers (these are two separate things) and modify them accordingly. +### **9. Send out the newsletter** +Send out an email to the 'GitLab Newsletter' mailing list on MailChimp. +Replicate the former release newsletter and modify it accordingly. Include a link to the blog post and keep it short. -Proposed email for CE: "We have released a new version of GitLab Community Edition and its packages. See our blog post(<link>) for more information." +Proposed email text: +"We have released a new version of GitLab. See our blog post(<link>) for more information." # **23rd - Optional Patch Release** diff --git a/doc/release/patch.md b/doc/release/patch.md index 7762c9f0e11..9ffa7d2f606 100644 --- a/doc/release/patch.md +++ b/doc/release/patch.md @@ -27,4 +27,5 @@ Otherwise include it in the monthly release and note there was a regression fix 1. [Build new packages with the latest version](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/release.md) 1. Cherry-pick the changelog update back into master 1. Send tweets about the release from `@gitlabhq`, tweet should include the most important feature that the release is addressing as well as the link to the changelog -1. Note in the 'GitLab X.X regressions' issue that the patch was published(CE only) +1. Note in the 'GitLab X.X regressions' issue that the patch was published (CE only) +1. Send out an email to the 'GitLab Newsletter' mailing list on MailChimp diff --git a/doc/release/security.md b/doc/release/security.md index 5265ca82eba..3944f55e03f 100644 --- a/doc/release/security.md +++ b/doc/release/security.md @@ -18,9 +18,8 @@ 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 subscribers mailing list on MailChimp +1. Send out an email to the 'GitLab Newsletter' mailing list on MailChimp 1. Send out an email to [the community google mailing list](https://groups.google.com/forum/#!forum/gitlabhq) -1. Send out an email to [the GitLab newsletter list](http://gitlab.us5.list-manage.com/subscribe?u=498dccd07cf3e9482bee33ba4&id=98a9a4992c) 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/) 1. Thank the security researcher in an email for their cooperation |