Merge branch 'add_tweet_and_alert_message_tasks_to_release_issue' into 'master'

Add announce the deployment to monthly issue

See merge request !127

templates/monthly.md.erb

@@ -43,6 +43,9 @@ Stable branch should be created after the 7th. The 7th is the last date to relia
   - [ ] Ensure tests are green on [EE stable branch]
   - [ ] Ensure tests are green on [Omnibus CE stable branch]
   - [ ] Ensure tests are green on [Omnibus EE stable branch]
+  - [ ] Make sure to [announce the deployment] on Twitter and GitLab.com
+    * With downtime: 1 hour before
+    * Without downtime: 15 minutes before
   - [ ] In `#releases`: I'm going to tag `<%= version.to_rc %>`
   - [ ] Tag the `<%= version.to_rc %>` version using the [`release` task]:
@@ -56,14 +59,15 @@ Stable branch should be created after the 7th. The 7th is the last date to relia
         # In the chef-repo project:
         bundle exec rake "deploy[staging, <%= version.to_rc %>.ee.0]"
         ```
-  - [ ] [Deploy] [`<%= version.to_rc %>`](https://packages.gitlab.com/gitlab/unstable/packages/ubuntu/xenial/gitlab-ee_<%= version.to_rc %>.ee.0_amd64.deb) to [staging.gitlab.com]
+  - [ ] Do the [deploy] of [`<%= version.to_rc %>`](https://packages.gitlab.com/gitlab/unstable/packages/ubuntu/xenial/gitlab-ee_<%= version.to_rc %>.ee.0_amd64.deb) to [staging.gitlab.com]
   - [ ] In `#production`: I'm going to deploy `<%= version.to_rc %>` to production
         ```sh
         # In the chef-repo project:
         bundle exec rake "deploy[production, <%= version.to_rc %>.ee.0]"
         ```
-  - [ ] [Deploy] [`<%= version.to_rc %>`](https://packages.gitlab.com/gitlab/unstable/packages/ubuntu/xenial/gitlab-ee_<%= version.to_rc %>.ee.0_amd64.deb) to GitLab.com
-  - [ ] Tweet about the `<%= version.to_rc %>` release:
+  - [ ] Tweet about the deploy, at this point the deploy alert banner on GitLab.com should already be up.
+  - [ ] Do the [deploy] of [`<%= version.to_rc %>`](https://packages.gitlab.com/gitlab/unstable/packages/ubuntu/xenial/gitlab-ee_<%= version.to_rc %>.ee.0_amd64.deb) to GitLab.com
+  - [ ] Post a [tweet about] the `<%= version.to_rc %>` release:
         ```
         GitLab <%= version.to_rc %> is available: https://packages.gitlab.com/gitlab/unstable
@@ -136,6 +140,9 @@ cherry-picked into `<%= version.stable_branch %>`.
   - [ ] Ensure tests are green on [EE stable branch]
   - [ ] Ensure tests are green on [Omnibus CE stable branch]
   - [ ] Ensure tests are green on [Omnibus EE stable branch]
+  - [ ] Make sure to [announce the deployment] on Twitter and GitLab.com
+    * With downtime: 1 hour before
+    * Without downtime: 15 minutes before
   - [ ] In `#releases`: I'm going to tag `<%= version.to_rc(2) %>`
   - [ ] Tag the `<%= version.to_rc(2) %>` version using the [`release` task]:
@@ -155,8 +162,9 @@ cherry-picked into `<%= version.stable_branch %>`.
       # In the chef-repo project:
       bundle exec rake "deploy[production, <%= version.to_rc(2) %>.ee.0, gitlab/unstable]"
       ```
-- [ ] [Deploy] [`<%= version.to_rc(2) %>`](https://packages.gitlab.com/gitlab/unstable/packages/ubuntu/xenial/gitlab-ee_<%= version.to_rc(2) %>.ee.0_amd64.deb) to GitLab.com
-- [ ] Tweet about the `<%= version.to_rc(2) %>` release:
+- [ ] Tweet about the deploy, at this point the deploy alert banner on GitLab.com should already be up.
+- [ ] Do the [deploy] [`<%= version.to_rc(2) %>`](https://packages.gitlab.com/gitlab/unstable/packages/ubuntu/xenial/gitlab-ee_<%= version.to_rc(2) %>.ee.0_amd64.deb) to GitLab.com
+- [ ] Post a [tweet about] the `<%= version.to_rc(2) %>` release:
       ```
       GitLab <%= version.to_rc(2) %> is available: https://packages.gitlab.com/gitlab/unstable
@@ -178,6 +186,9 @@ This way we ensure the release does not introduce new regressions.
   - [ ] Ensure tests are green on [EE stable branch]
   - [ ] Ensure tests are green on [Omnibus CE stable branch]
   - [ ] Ensure tests are green on [Omnibus EE stable branch]
+  - [ ] Make sure to [announce the deployment] on Twitter and GitLab.com
+    * With downtime: 1 hour before
+    * Without downtime: 15 minutes before
   - [ ] In `#releases`: I'm going to tag `<%= version.to_patch %>`
   - [ ] Tag the `<%= version.to_patch %>` version using the [`release` task]:
@@ -189,9 +200,10 @@ This way we ensure the release does not introduce new regressions.
 - Before 07:00 Pacific (mostly 16:00 CET):
   - [ ] In `#production`: I'm going to deploy `<%= version.to_patch %>` to staging
-  - [ ] [Deploy] [`<%= version.to_patch %>`](https://packages.gitlab.com/gitlab/gitlab-ee/packages/ubuntu/xenial/gitlab-ee_<%= version.to_patch %>-ee.0_amd64.deb) to [staging.gitlab.com]
+  - [ ] Do the [deploy] of [`<%= version.to_patch %>`](https://packages.gitlab.com/gitlab/gitlab-ee/packages/ubuntu/xenial/gitlab-ee_<%= version.to_patch %>-ee.0_amd64.deb) to [staging.gitlab.com]
   - [ ] In `#production`: I'm going to deploy `<%= version.to_patch %>` to production
-  - [ ] [Deploy] [`<%= version.to_patch %>`](https://packages.gitlab.com/gitlab/gitlab-ee/packages/ubuntu/xenial/gitlab-ee_<%= version.to_patch %>-ee.0_amd64.deb) to GitLab.com
+  - [ ] Tweet about the deploy, at this point the deploy alert banner on GitLab.com should already be up.
+  - [ ] Do the [deploy] of [`<%= version.to_patch %>`](https://packages.gitlab.com/gitlab/gitlab-ee/packages/ubuntu/xenial/gitlab-ee_<%= version.to_patch %>-ee.0_amd64.deb) to GitLab.com
   - [ ] Create the `<%= version.to_patch %>` version on https://version.gitlab.com
   - [ ] Create the first patch issue using the [`patch_issue` task]:
@@ -212,8 +224,10 @@ This way we ensure the release does not introduce new regressions.
 [EE stable branch]: https://dev.gitlab.org/gitlab/gitlab-ee/commits/<%= version.stable_branch(ee: true) %>
 [Omnibus CE stable branch]: https://dev.gitlab.org/gitlab/omnibus-gitlab/commits/<%= version.stable_branch %>
 [Omnibus EE stable branch]: https://dev.gitlab.org/gitlab/omnibus-gitlab/commits/<%= version.stable_branch(ee: true) %>
+[announce the deployment]: https://dev.gitlab.org/cookbooks/chef-repo/blob/master/doc/deploying.md#announce-the-deployment
 [CE packages are built]: https://dev.gitlab.org/gitlab/omnibus-gitlab/commits/<%= version.stable_branch %>
 [EE packages are built]: https://dev.gitlab.org/gitlab/omnibus-gitlab/commits/<%= version.stable_branch(ee: true) %>
+[tweet about]: https://dev.gitlab.org/cookbooks/chef-repo/blob/master/doc/deploying.md#announce-that-the-deploy-is-done
 [`gitlab/unstable`]: https://packages.gitlab.com/gitlab/unstable
 [`new_release_post` task]: https://gitlab.com/gitlab-com/www-gitlab-com/#create-release-blog-post
 [`www-gitlab-com` project]: https://gitlab.com/gitlab-com/www-gitlab-com/
@@ -229,5 +243,5 @@ This way we ensure the release does not introduce new regressions.
 [`regression_issue` task]: https://gitlab.com/gitlab-org/release-tools/blob/master/doc%2Frake-tasks.md#regression_issueversion
 [MVP page]: https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/source/mvp/index.html
 [`Pick into Stable` <%= version.to_minor %> merged merge requests]: https://gitlab.com/groups/gitlab-org/merge_requests?label_name%5B%5D=Pick+into+Stable&milestone_title=<%= version.milestone_name %>&scope=all&sort=id_desc&state=merged
-[Deploy]: https://dev.gitlab.org/cookbooks/chef-repo/blob/master/doc/deploying.md
+[deploy]: https://dev.gitlab.org/cookbooks/chef-repo/blob/master/doc/deploying.md
 [staging.gitlab.com]: https://staging.gitlab.com/