5.x-final.md, 5.x-patch.md - Start publishing ESR releases sooner (#19)

doc/5.x-final.md

@@ -47,34 +47,28 @@ For example, we might pick `gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.js
 
 ## 4: Publish
 
-You can do the full process in one command:
+For a typical release, you can run the full process in one command:
 
 ```
 cd ~/src/master
 releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json get sign tag publish
 ```
 
-or do the steps individually:
+If this branch will have future ESR support, then you should also publish releases to `lab.c.o/esr/*`.
 
 ```
-cd ~/src/master
-
-## Download and rename the RC tarballs
-releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json get
+releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json get sign tag publish esr-tag esr-publish
+```
 
-## Generate signatures for tarballs
-releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json sign
+Note: You may run tasks individually, and you may do dry-runs (`--dry-run`/`-N`). For example
 
-## Generate tags in each repo (dry run)
-releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json tag -N
+```
+cd ~/src/master
 
-## Publish tarballs to Sourceforge and Gcloud (dry run)
+## Publish tarballs to Google Cloud and Sourceforge (dry run)
 releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json publish -N
 
-## Generate tags in each repo (really)
-releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json tag -f
-
-## Publish tarballs to Sourceforge and Gcloud (really)
+## Publish tarballs to Google Cloud and Sourceforge (really)
 releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json publish
 ```
 

doc/5.x-patch.md

@@ -83,34 +83,28 @@ For example, we might pick `gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.js
 
 ## 4: Publish
 
-You can do the full process in one command:
+For a typical release, you can run the full process in one command:
 
 ```
 cd ~/src/master
 releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json get sign tag publish
 ```
 
-or do the steps individually:
+If this branch will have future ESR support, then you should also publish releases to `lab.c.o/esr/*`.
 
 ```
-cd ~/src/master
-
-## Download and rename the RC tarballs
-releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json get
+releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json get sign tag publish esr-tag esr-publish
+```
 
-## Generate signatures for tarballs
-releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json sign
+Note: You may run tasks individually, and you may do dry-runs (`--dry-run`/`-N`). For example
 
-## Generate tags in each repo (dry run)
-releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json tag -N
+```
+cd ~/src/master
 
-## Publish tarballs to Sourceforge and Gcloud (dry run)
+## Publish tarballs to Google Cloud and Sourceforge (dry run)
 releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json publish -N
 
-## Generate tags in each repo (really)
-releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json tag -f
-
-## Publish tarballs to Sourceforge and Gcloud (really)
+## Publish tarballs to Google Cloud and Sourceforge (really)
 releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json publish
 ```