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: 
  A positive vote for a particular release from the TinkerPop PMC is required to move to the following phase.
  
  . By this point, the testing performed during the code freeze should have validated the release.  If however there
  are additional tests to perform that the release manager feels are relevant, they should be performed now. In other
  words, there is no need to rebuild the `SNAPSHOT` yet another time unless there are circumstances that would call its
  validity into question.
  . Update `CHANGELOG.asciidoc`:
  .. Update the release date
  .. Generate the JIRA release notes report for the current version and append them to the `CHANGELOG.asciidoc`.
  ... Use an "advanced" search to filter out JIRA issues already released on other versions. For example: `fixVersion
  = 3.1.0-incubating AND fixVersion not in (3.0.2-incubating, 3.0.1-incubating`.
  ... Consider use of an "Excel" export to organize, sort and prepare the JIRA tickets to be pasted to `CHANGELOG.asciidoc`
  ... Be sure to include a link to other versions in the `CHANGELOG.asciidoc` that were previously released while the
  current release was under development as this new release will have those changes included within it. Please see
  3.1.0-incubating for an example.
  .. Organize "breaking" changes to be clearly marked (use JIRA and the "breaking" label to identify those)
  . Update "upgrade documentation":
  .. Update the release date.
  