anchor.diff:      mvn release:prepare -Dresume=false ...
   
   See http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html
  +
  +=== Pre-check created Jars
  +
  +It's best to run check_jars.sh prior to creating (and staging) the 
  +Release Candidate. 
  +
  +    buildTools/check_jars.sh --findmode build-release 1.2.0 .
  +    
  +If there are any problems raise the issues on the "[DISCUSS]" thread.  If the decision is to make changes now, address them, remove the release tag and redo the Prepare.
  +    
  +    Remove the release tag:
  +
  +    git push --delete origin <tag>   # delete the remote tag
  +    git tag --delete <tag>           # delete the local tag
  +    
   
   == Create and Stage the Release Candidate
   
  
positive.code: 
  == 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.
  
  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.
  
  
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
  
  