Update pagure release process

Include generation of document in docs/Releases and clean up
formatting of document.

Signed-off-by: Robbie Harwood <[email protected]>

Author: frozencemetery

docs/ReleaseProcess.md

@@ -7,45 +7,56 @@ project's git repository.
 
 ## Version and Tag the release
 
-- Commit a change in version.m4 with the new version number (ex. 0.1.0)
+- Change in version.m4 with the new version number (ex. 0.1.0)
+
+- Create a docs/Releases page with highlights and a full changelog with the
+  command:
+
+```
+git shortlog <oldtag>..
+```
+
+- Commit version.m4 and the new Releases page
 
 - Test locally with "make rpms" that everything builds fine
 
 - Tag the release in master like this:
+
 ```
 git tag v0.1.0
 ```
+
   This will apply the tag to the last commit
 
 - Push the tag:
+
 ```
 git push origin v0.1.0
 ```
 
 ## Create a release tarball and SHA hash
 
 - Run the following commands (on a git clean tree, please):
+
 ```
 autoreconf -f -i
 ./configure
 make dist
 make distcheck
 ```
+
   ... will generate a tarball named like: gssproxy-0.1.0.tar.gz
+
 ```
 sha512sum gssproxy-0.1.0.tar.gz > gssproxy-0.1.0.tar.gz.sha512sum.txt
 ```
+
   ... will generate a file with a sha512 checksum
 
 ## Publish the release
 
 - Upload tarball and checksum to Pagure release page
 
-- Create a Release page with highlights and a full changelog with the command:
-```
-git shortlog <oldtag>..<newtag>
-```
-
 - Copy the content of the new-release page into a mail and announce on the
   gssproxy mailinglist
   (https://lists.fedorahosted.org/mailman/listinfo/gss-proxy)