anchor.diff:      login to https://repository.apache.org/  with your Apache credentials
       select "Staging Repositories" in the section "Build Promotion"
       click on the orgapacheedgent-#### staging repository
  -    click on the Close button
  +    click on the Close button  #  set the description to "Apache Edgent X.Y.Z-RC<n>"
   
   A number of pre-configured tests are executed automatically:
   
  
positive.code: 
  In this phase on the release branch, the poms Edgent versions are changed to the specified release version, a full build with all tests is run, and a commit is done with this state and tagged. After that the release branch poms Edgent versions are set to the first/next specified `major.minor.bugfix-SNAPSHOT` bugfix development version and this update is committed.  The commits are automatically pushed.
  
  WARNING: at this moment the new edgent-deployment-filter-maven-plugin (EDGENT-440) is not yet released and the release:prepare below will fail with `There are still some remaining snapshot dependencies.`  To work around that for the moment, add `-DignoreSnapshots` to the `mvn release:prepare` below.  I'm not sure but prior to doing the prepare you may need to build the plugin and install it in your maven cache (`cd utils/edgent-deployment-filter-maven-plugin; mvn install`).
  
  Prepare the release branch:
  
      git checkout release/1.2  # the branch from "Creating the Release Branch"
      
      mvn release:prepare -DreleaseVersion=1.2.0 -Dtag=edgent-1.2.0 -DdevelopmentVersion=1.2.1-SNAPSHOT -DautoVersionSubmodules=true -P platform-android,platform-java7,distribution 
      
      git status  # should report nothing ahead/behind. Do 'git push' if needed.
  
  Now would be a good time to update the "[DISCUSS]" thread with the branch and tag info if you so choose.
  
  
negative.code: === Unwanted Staged Artifacts
  
  The `release:perform` stages some undesired artifacts.  See EDGENT-440.
  
  Minimally, log into Nexus and select the staging repository as described below in `Close the Staging Repository`, and manually select and delete the various `source-release` files in `org/apache/edgent/edgent-parent` using the browser UI.
  
  