4.7-{final,rc}.md - More tweaks

doc/4.7-final.md

@@ -27,14 +27,14 @@ For example, we might pick `gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-20170503
 You can do the full process in one command:
 
 ```
-cd /path/to/civicrm
+cd ~/src/4.7
 releaser gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json --get --sign --tag --publish
 ```
 
 or do the steps individually:
 
 ```
-cd /path/to/civicrm
+cd ~/src/4.7
 
 ## Download and rename the RC tarballs
 releaser gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json --get
@@ -55,6 +55,17 @@ releaser gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json --tag -f
 releaser gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json --publish
 ```
 
+You might want to spot-check a few URLs to ensure the tags were published, e.g.
+
+ * https://github.com/civicrm/civicrm-backdrop/tree/1.x-4.7.X
+ * https://github.com/civicrm/civicrm-core/tree/4.7.X
+ * https://github.com/civicrm/civicrm-drupal/tree/6.x-4.7.X
+ * https://github.com/civicrm/civicrm-drupal/tree/7.x-4.7.X
+ * https://github.com/civicrm/civicrm-drupal/tree/8.x-4.7.X
+ * https://github.com/civicrm/civicrm-joomla/tree/4.7.X
+ * https://github.com/civicrm/civicrm-packages/tree/4.7.X
+ * https://github.com/civicrm/civicrm-wordpress/tree/4.7.X
+
 ## 3: Set default on `civicrm.org` (WIP)
 
 ... login to `latest` and update versions.json ...

doc/4.7-rc.md

@@ -5,6 +5,8 @@
  * Write access to all main CiviCRM git repos (civicrm-{core,packages,backdrop,drupal,joomla,wordpress})
  * Access to CiviCRM Jenkins (https://test.civicrm.org)
 
+The user `releaser` on `latest.civicrm.org` has a suitable configuration in `~/src/4.7`.
+
 ## 1: Sanity checks
 
  * Note the original branch, such as `master`.
@@ -39,7 +41,7 @@ A safe way to make a clean copy of every repo is to create a new `dist` build:
 ```bash
 ## Clone all the repos. Ensure that you have a clean, up-to-date copy of the `master` branch.
 civibuild create dist 
-cd ~/buildkit/build/dist/src
+cd ~/src/4.7
 git scan foreach -c 'pwd; git branch; echo'
 git scan status
  
@@ -63,6 +65,17 @@ git scan push -p origin 4.7.X-rc -n -T
 git scan push -p origin 4.7.X-rc
 ```
 
+You might want to spot-check a few URLs to ensure the branches were published, e.g.
+
+ * https://github.com/civicrm/civicrm-backdrop/tree/1.x-4.7.X-rc
+ * https://github.com/civicrm/civicrm-core/tree/4.7.X-rc
+ * https://github.com/civicrm/civicrm-drupal/tree/6.x-4.7.X-rc
+ * https://github.com/civicrm/civicrm-drupal/tree/7.x-4.7.X-rc
+ * https://github.com/civicrm/civicrm-drupal/tree/8.x-4.7.X-rc
+ * https://github.com/civicrm/civicrm-joomla/tree/4.7.X-rc
+ * https://github.com/civicrm/civicrm-packages/tree/4.7.X-rc
+ * https://github.com/civicrm/civicrm-wordpress/tree/4.7.X-rc
+
 ## 3: Publish tarballs
 
  * Go to https://test.civicrm.org/job/CiviCRM-Publish/
@@ -76,9 +89,14 @@ git scan push -p origin 4.7.X-rc
 The original branch, "master", should continue development with the next version, e.g. "4.7.Y".
 
 ```bash
-cd ~/buildkit/build/dist/src
+cd ~/src/4.7
 git checkout master
 git pull --ff-only origin master
 ./tools/bin/scripts/set-version.php 4.7.Y --commit
 git push origin master
 ```
+
+## 5: Setup automated tests
+
+ * Go to https://test.civicrm.org/job/CiviCRM-Core-Matrix/configure
+ * In the list of `CIVIVER`s, remove any old RC's. Add the current RC.