Update 4.6-final.md and 4.7-final.md

Changes:
 * Add step #s.
 * In `4.6`, include the "Sanity Check". This is already addressed in `4.7`, but they need to do it at different times (`rc` vs `final`).

doc/4.6-final.md

@@ -12,7 +12,18 @@
 
 The user `releaser` on `latest.civicrm.org` has a suitable configuration in `~/src/4.6`.
 
-## Identify the final RC
+## 1: Sanity checks
+
+ * Note the original branch, such as `4.6`.
+ * Note the intended version, such as `4.6.28` or `4.6.29`.
+   * In civicrm-core.git repo, check that the code in `master` correctly references `4.6.X`:
+     * https://github.com/civicrm/civicrm-core/blob/master/xml/version.xml
+     * https://github.com/civicrm/civicrm-core/blob/master/sql/civicrm_generated.mysql
+     * https://github.com/civicrm/civicrm-core/tree/master/CRM/Upgrade/Incremental
+   *  In Jenkins, review the scheduled tests for `4.6` and determine if anything should block the RC.
+     * https://test.civicrm.org/job/CiviCRM-Core-Matrix/
+
+## 2: Identify the final RC
 
 Determine the identity of the final release candidate:
 
@@ -22,7 +33,7 @@ gsutil ls gs://civicrm-build/4.6/*json
 
 For example, we might pick `gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json`.
 
-## Publish
+## 3: Publish
 
 You can do the full process in one command:
 
@@ -55,11 +66,11 @@ releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --tag -f
 releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --publish
 ```
 
-## Set default on `civicrm.org` (WIP)
+## 4: Set default on `civicrm.org` (WIP)
 
 ... login to `latest` and update versions.json ...
 
-## Bump version
+## 5: Bump version
 
 ```
 cd ~/src/4.6

doc/4.7-final.md

@@ -12,7 +12,7 @@
 
 The user `releaser` on `latest.civicrm.org` has a suitable configuration in `~/src/4.7`.
 
-## Identify the final RC
+## 1: Identify the final RC
 
 Determine the identity of the final release candidate:
 
@@ -22,7 +22,7 @@ gsutil ls gs://civicrm-build/*rc/*json
 
 For example, we might pick `gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json`.
 
-## Publish
+## 2: Publish
 
 You can do the full process in one command:
 
@@ -55,11 +55,11 @@ 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
 ```
 
-## Set default on `civicrm.org` (WIP)
+## 3: Set default on `civicrm.org` (WIP)
 
 ... login to `latest` and update versions.json ...
 
-## Set default on `sourceforge.net`
+## 4: 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.