update release instructions to merge readme branch before tagging the release

Author: WalkerCodeRanger

PublishingRelease.md

@@ -9,10 +9,12 @@
 
 ## Steps to Publish Release
 
-1. Create an *annotated* tag of the version number being published prefixed with "v". The tag description should match the tag name.
-2. Wait for the build of that tag to complete in Appveyor.
-3. Download the nupkg and snupkg files from the assets tab of Appveyor.
-4. Upload those to NuGet with the new readme from the readme branch.
+1. Merge the `vX.Y.Z-readme` branch into `master`.
+2. Create an *annotated* tag of the version number being published prefixed with "v". The tag
+   description should match the tag name.
+3. Wait for the build of that tag to complete in Appveyor.
+4. Download the nupkg and snupkg files from the assets tab of Appveyor.
+5. Upload those to NuGet with the new readme.
    * Remove the build and NuGet status from the top of the readme before putting it in NuGet.
 
 ## After Publishing a Release
@@ -22,8 +24,7 @@ These steps only need to be done for a non-prerelease version.
 1. Create a release from the tag on github.
    * Write up the changes in that version.
    * Attach the nupkg and snupkg files to the release in github.
-2. Merge the `vX.Y.Z-readme` branch into `master`.
-3. Create a new `vX.Y.Z-readme` branch for the next version.
-4. Mark the milestone, and any included issues, done with the current date.
-5. Update the `PublicAPI` files to reflect the newly published APIs
-6. Update the benchmark to reference the new version as the previous version.
+2. Create a new `vX.Y.Z-readme` branch for the next version.
+3. Mark the milestone, and any included issues, done with the current date.
+4. Update the `PublicAPI` files to reflect the newly published APIs
+5. Update the benchmark to reference the new version as the previous version.