James pointed out this was lacking in my release process document. I've
added a note about the leading v in the annotated tag as per
http://semver.org/
The release process document didn't really mention semver.org or the
rubrics we use to pick version numbers at release. This patch adds some
hints about picking a version number and looking for API breaking
changes to the code.