anchor.diff:  
   == Cleanup Hints
   
  -If you wish to completely reset your repository back to the way it was before doing any of these release process steps it can be done with a little work.
  +If you wish to completely reset the source repository back to the way it was before doing any of these release process steps it can be done with a little work.
   
   Due to the way that the plugin works, even creating the release branch results in changes committed and (auto) pushed to the `develop` branch (advancing the poms Edgent versions to the next development version).  Sigh.
   
  
positive.code: 
  See the Release Manager's Guide for information on publishing the staged source release bundles and merging an approved release to the `master`, and possibly `develop`, branches.
  
  == Actions if the vote failed
  
  If something popped up during the vote on the release and the release candidate has to be dropped, two things have to be done:
  
  
negative.code: 
  Notes:
  
  * -DbranchName : the name of the release branch - release/<major>.<minor>
  * -DautoVersionSubmodules : all children modules inherit the the top level pom's version
  * -P platform-android,... : these profiles are required so that all modules are processed
  
  