5.x-patch.md

doc/5.x-patch.md

@@ -25,11 +25,19 @@ git cherry-pick abcd1234abcd1234
 git push origin 5.X
 ```
 
-## 3: Prepare and identify the final tarballs
+## 3: (If you haven't already) Validate test results
+
+In Jenkins, check the test results for the `5.X` branch:
+
+* https://test.civicrm.org/job/CiviCRM-Core-Matrix/
+
+Tip: If you just merged/pushed changes, you may want to trigger a new test run.
+
+## 4: Prepare and identify the final tarballs
 
 In Jenkins, ensure that the final tarballs have been prepared. Run the job manually if you're impatient.
 
-    * https://test.civicrm.org/job/CiviCRM-Publish/
+* https://test.civicrm.org/job/CiviCRM-Publish/
 
 After running, determine the identity of the final build:
 
@@ -39,7 +47,7 @@ gsutil ls gs://civicrm-build/5.2/*json
 
 For example, we might pick `gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json`.
 
-## 4: Publish
+## 5: Publish
 
 You can do the full process in one command:
 
@@ -83,7 +91,7 @@ You might want to spot-check a few URLs to ensure the tags were published, e.g.
 * https://github.com/civicrm/civicrm-packages/tree/5.X.1
 * https://github.com/civicrm/civicrm-wordpress/tree/5.X.1
 
-## 5: Update `versions.json`
+## 6: Update `versions.json`
 
 Services such as the `civicrm.org` download page and the in-app version
 check depend on a file named `versions.json`. Update this.
@@ -102,7 +110,7 @@ git commit versions.json
 git push origin master
 ```
 
-## 6: Set default on `sourceforge.net`
+## 7: Set default on `sourceforge.net`
 
 Log into https://sourceforge.net/projects/civicrm/files/civicrm-stable and set the latest Drupal version to be the default download.