anchor.diff:  . `mvn versions:set -DnewVersion=x.y.z -DgenerateBackupPoms=false` to update project files to reference the non-SNAPSHOT version
   . `git diff` and review the updated files (expect all `pom.xml` files and this README)
   . `git commit -a -m "TinkerPop x.y.z release"` and `git push`
  -. `git tag -a -m "TinkerPop x.y.z release" x.y.z` and `git push --tags`
   . `mvn clean install -Dmaven.test.skip=true` - need to build first so that the right version of the console is used with `bin/publish-docs.sh`
  -. `bin/publish-docs.sh <username>`
  -. `mvn install -Papache-release -Djavadoc -DcreateChecksum=true -Dmaven.test.skip=true`
  -. `mvn deploy -Papache-release -DcreateChecksum=true -Dmaven.test.skip=true`- deploy signed artifacts with checksums to link:https://repository.apache.org/[Apache Nexus]. Review (artifacts versions, file sizes, anything that might be out of place - request another committer to review as well) but do NOT close/release the staging repository at this time.
  +. `bin/process-docs.sh` and validate the generated documentation locally
  +. `bin/publish-docs.sh <username>` - Note that this step requires no additional processing as the previous step.
  +handled document generation and this step now merely needs to upload what was generated.
  +. `mvn deploy -Papache-release -DcreateChecksum=true -Dmaven.test.skip=true` - deploy signed artifacts with checksums to link:https://repository.apache.org/[Apache Nexus]. Review (artifacts versions, file sizes, anything that might be out of place - request another committer to review as well) but do NOT close/release the staging repository at this time.
   . Review generated artifacts to be sure they have both javadocs and asciidocs present
   . Upload artifacts to `https://dist.apache.org/repos/dist/dev/incubator/tinkerpop` for `[VOTE]` review.
   .. `svn co --depth empty https://dist.apache.org/repos/dist/dev/incubator/tinkerpop/ dev` and `mkdir dev/x.y.z`
  
positive.code: .. pass:[<code>ls * | xargs -n1 -I {} echo "mv apache-{} {}" | sed -e 's/distribution/bin/' -e 's/source-release/src/' -e s'/^\(.*\) \(.*\) \(.*\)$/\1 \3 \2/' | /bin/bash</code>]
  .. `cd ..; svn add x.y.z/; svn ci -m "TinkerPop x.y.z release"`
  . Execute `bin/validate-distribution.sh` and any other relevant testing.
  . Perform JIRA administration tasks:
  .. "Release" the current version and set the "release date"
  .. If there is to be a follow on release in the current line of code, create that new version specifying the "start date"
  .. Migrate the "Affected Version" of all unresolved issues to the next lowest common denominator version - if version 3.0.1 released then all 3.0.0 issues should move forward to 3.0.1 as they now "affect" that latest release
  . Submit for `[VOTE]` at `dev@tinkerpop.incubator.apache.org` (see email template below)
  . *Wait for vote acceptance* (72 hours)
  
  
negative.code: .. Deploy a final SNAPSHOT to the snapshot repository.
  .. Review LICENSE and NOTICE files to make sure that no <<dependencies,changes are needed>>.
  .. Review javadoc filters on the "Core API" docs to be sure nothing needs to change.
  .. Review JIRA tickets in the release and ensure that:
  ... All tickets categorized by having a "Component" assigned.
  ... All tickets are either of type "Bug" or "Enhancement".
  . When all documentation changes are in place, use `bin/publish-docs.sh` to deploy a final `SNAPSHOT` representation
  of the docs and thus validate that there are no issues with the documentation generation process. Request review
  of the published documentation on the dev mailing list.
  