docs: Remove IRC notification (mozilla#1646)

onstash · Nov 2, 2018 · b9843de · b9843de
1 parent a8b8789
commit b9843de
Showing 1 changed file with 8 additions and 52 deletions.
diff --git a/src/docs/deploy/regular.rst b/src/docs/deploy/regular.rst
@@ -57,31 +57,7 @@ removing `-unprotected` suffix as shown bellow.
 .. _`go to Github`: https://github.com/mozilla/release-services/settings/branch_protection_rules/2244704
 
 
-3. Notify about to start staging deployment
--------------------------------------------
-
-.. todo:: This step is not going to be needed once we finish `#1565`_
-
-To coordinate and inform others please send a message to others in ``#release-services`` IRC channel.
-
-::
-
-  I have pushed to staging branch. Until tomorrow, when we deploy to production, staging branch is closed. You can follow the progress at <LINK_TASKCLUSTER_GRAPH>.
-
-You should provide `<LINK_TASKCLUSTER_GRAPH>` which you can find under Commit status icon on staging branch, example is shown bellow.
-
-.. image:: step_3_page_listing_commits_of_staging_branch.png
-
-Also copy past link to tracking Pull Request of the deployment under respective
-build number as shown bellow.
-
-
-.. image:: step_3_taskcluster_graph_link.png
-
-.. -`#1565`: https://github.com/mozilla/release-services/issues/1565
-
-
-4. Verify if projects are working on staging
+3. Verify if projects are working on staging
 --------------------------------------------
 
 Before we push to production, we verify that projects are working on staging.
@@ -101,27 +77,7 @@ The role of the release manager is that it ensures that all projects are
 verified and tested before deploying to production.
 
 
-5. Announce new deployment to teams that help us monitor projects
------------------------------------------------------------------
-
-.. todo:: This step wont be needed once `#1568`_ is implemented
-
-Once all project have been tested successfully on staging only then we can
-proceed further.
-
-Announce that deployment to production is going to happen shortly:
-
-- on ``#ci`` IRC channel. when
-- and on ``#moc`` IRC channel
-
-You can use the following message:::
-
-  I am about to release a new version of mozilla/release-services (*.mozilla-releng.net, *.moz.tools). Any alerts coming up soon will be best directed to me. I'll let you know when it's all done. Thank you!
-
-.. _`#1568`: https://github.com/mozilla/release-services/issues/1568
-
-
-6. Deploy projects to production
+4. Deploy projects to production
 --------------------------------
 
 To deploy all project to production we need to push respected code to
@@ -144,7 +100,7 @@ Request of the deployment as shown below.
 .. image:: step_6_taskcluster_graph_link.png
 
 
-7. Verify if projects are working on production
+5. Verify if projects are working on production
 -----------------------------------------------
 
 Each project is verified and reported back to the tracking Pull Request of
@@ -162,10 +118,10 @@ The role of the release manager is that it ensures that all projects are
 verified and tested before deploying to production.
 
 
-8. Announce that deployment to production is done
+6. Announce that deployment to production is done
 -------------------------------------------------
 
-Announce that deployment to production is done:
+An automatic IRC message has been sent by Taskcluster when starting the deployment. You need to announce that deployment to production is now done:
 
 - on ``#ci`` IRC channel. when
 - and on ``#moc`` IRC channel
@@ -175,7 +131,7 @@ You can use the following message:::
   Previously annonced release of mozilla/release-services (*.mozilla-releng.net, *.moz.tools) to productions is now complete. If you see anything behaving weird please let me know.
 
 
-9. Write the release notes
+7. Write the release notes
 --------------------------
 
 `Create the release notes`_ on GitHub and use tag we created in step 7.
@@ -192,7 +148,7 @@ A good starting point for writing release notes is:
 .. _`Create the release notes`: https://github.com/mozilla/release-services/releases/new
 
 
-10. Push new base image
+8. Push new base image
 -----------------------
 
 This step will take some time (~30-60min) also good Internet connection is
@@ -227,7 +183,7 @@ image is quite big (~1.5GB). When it fails you can only retrigger the
     docker push mozillareleng/services:base-$(cat ./VERSION)
 
 
-11. Bump version
+9. Bump version
 ----------------
 
 Once base image is pushed to Docker Hub we can merged tracking Pull Request of