summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSytse Sijbrandij <sytse@gitlab.com>2014-10-24 20:32:07 +0000
committerSytse Sijbrandij <sytse@gitlab.com>2014-10-24 20:32:07 +0000
commit6280b53f305e45d0e6c474dbcf684f0015aee385 (patch)
tree5c9ffaf2ccc6675bdbb5b111d382e2b85848d319
parentcc42edfa495703877143abc98c1b6dbf6862aa55 (diff)
parent250d582bdd40e25f0aa16c76fc7a6ff31b113c22 (diff)
downloadgitlab-ce-6280b53f305e45d0e6c474dbcf684f0015aee385.tar.gz
Merge branch 'update_patch_doc' into 'master'
Update patch release document See merge request !1218
-rw-r--r--doc/release/patch.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/release/patch.md b/doc/release/patch.md
index bcc14568fc8..3ee55028b1f 100644
--- a/doc/release/patch.md
+++ b/doc/release/patch.md
@@ -26,6 +26,6 @@ Otherwise include it in the monthly release and note there was a regression fix
1. Apply the patch to GitLab Cloud and the private GitLab development server
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. Create blog post
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. Send out an email to the 'GitLab Newsletter' mailing list on MailChimp (or the 'Subscribers' list if the patch is EE only)