anchor.diff:  
       git checkout release/1.2  # the branch from "Creating the release branch"
       
  -    # Hmm... does -DskipTests work with the following?  Tests take a long
  -    # time and normally one has just gone through them all in the Prepare step.
  -    
       mvn release:perform -DreleaseProfiles=platform-android,platform-java7
   
   After this step is successful, a Nexus staging repository named `orgapacheedgent-####` will have been created at at https://repository.apache.org and populated with all of the release candidate's artifacts. The last four digits are generated by Nexus.
  
positive.code: === Unwanted Staged Artifacts
  
  The `release:perform` stages some undesired artifacts.  See EDGENT-440.
  
  TODO: what's needed to manually delete these? "Delete" each via the UI?
  What about the state of the metadata artifacts, do they reference those deleted items?
  
  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.
  
  
negative.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.
  
  Prepare the release branch:
  
      git checkout release/1.2  # the branch from "Creating the Release Branch"
      
      # see note below for -DignoreSnapshots=true
      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.
  
  NOTE: the new edgent-deployment-filter-maven-plugin (EDGENT-440) is not yet released and the release:prepare will fail with `There are still some remaining snapshot dependencies.`  Add `-DignoreSnapshots=true` to the `mvn release:prepare` to workaround that.  Build the plugin first if there seem to be other issues (`cd utils/edgent-deployment-filter-maven-plugin; mvn install`).
  
  Now would be a good time to update the "[DISCUSS]" thread with the branch and tag info if you so choose.
  
  