Improved release notes.

Author: SteveIves

Documentation/CodeGen.chm

@@ -3,39 +3,37 @@ CodeGen Release Procedure (GitHub)
 
 This document defines the procedure for distributing a new release of CodeGen on GitHub.
 
-1.	Complete all development for the new version.
+1.  Insert the USB code signing key and verify that the SafeNet Authentication Client is running before starting Visual Studio.
 
-2.  TEST TEST TEST!!!
+2.  Commit all software changes to the local repo
 
-3.  Commit all software changes to the local repo
+3.  Push the software changes to the GitHub repo
 
-5.  Push the software changes to the GitHub repo
+4.  Update the documentation (new features, release notes, version number, release date, etc.).
 
-6.  Update the documentation (new features, release notes, version number, release date, etc.).
+5.  Build new HTML help and Web help files.
 
-7.  Build new HTML help and Web help files.
+6.  Commit the documentation changes to the local repo with a comment of "Updated documentation in preparation for X.Y.Z release."
 
-8.  Commit the documentation changes to the local repo with a comment of "Updated documentation in preparation for X.Y.Z release."
+7.  Push the changes to the GitHub repo.
 
-9.  Push the changes to the GitHub repo.
+8.  Build everything in RELEASE mode.
 
-10. Build everything in RELEASE mode.
+9.  Build and sign a new installation.
 
-11. Insert the code signing certificate USB device and build a new installation.
+10. Install the new version and run as many tests as possible.
 
-12. Install the new version and run as many tests as possible.
+11. Copy the installer to the release history folder.
 
-13. Copy the installer to the release history folder.
+12. Do the release on GitHub.
 
-14. Do the release on GitHub.
+13. Upload web help files to the web site.
 
-15. Upload web help files to the web site.
+14. Bump the version number in CurrentRelease.xml
 
-16. Bump the version number in CurrentRelease.xml
+15. Commit the changes to CurrentRelease.xml to the local git repo with a comment of "Announced version X.Y.Z to check for update."
 
-17. Commit the changes to CurrentRelease.xml to the local git repo with a comment of "Announced version X.Y.Z to check for update."
-
-18. Push the changes to the GitHub repo.
+16. Push the changes to the GitHub repo.
 
 --------------------------------------------------------------------------------
 PREPARE TRUNK FOR NEXT VERSION