anchor.diff:  . Update "upgrade documentation":
   .. Update the release date.
   .. Update the link to CHANGELOG.asciidoc
  -. `mvn versions:set -DnewVersion=x.y.z -DgenerateBackupPoms=false` to update project files to reference the non-SNAPSHOT version
  +. `mvn versions:set -DnewVersion=xx.yy.zz -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`
  -. `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/process-docs.sh` and validate the generated documentation locally
  +. `git commit -a -m "TinkerPop xx.yy.zz release"` and push
  +. `mvn clean install` - need to build first so that the right version of the console is used with `bin/publish-docs.sh`
  +. `bin/process-docs.sh` and validate the generated documentation locally (don't rely on "SUCCESS" - scroll up through logs to ensure there were no errors and view the HTML directly)
   . `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.
  +. `mvn deploy -Papache-release -DcreateChecksum=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 then "close" the repo - if the repo is left open it will be automatically dropped after five days and closing the repo will allow it to stay available for a full ninety days which is more than enough time to complete a vote.
   . 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`
  -.. `cp ~/.m2/repository/org/apache/tinkerpop/gremlin-console/x.y.z/gremlin-console-x.y.z-distribution.zip* dev/x.y.z`
  -.. `cp ~/.m2/repository/org/apache/tinkerpop/gremlin-server/x.y.z/gremlin-server-x.y.z-distribution.zip* dev/x.y.z`
  -.. `cp ~/.m2/repository/org/apache/tinkerpop/tinkerpop/x.y.z/tinkerpop-x.y.z-source-release.zip* dev/x.y.z`
  -.. `cd dev/x.y.z`
  +.. `svn co --depth empty https://dist.apache.org/repos/dist/dev/incubator/tinkerpop/ dev` and `mkdir dev/xx.yy.zz`
  +.. `cp ~/.m2/repository/org/apache/tinkerpop/gremlin-console/xx.yy.zz/gremlin-console-xx.yy.zz-distribution.zip* dev/xx.yy.zz`
  +.. `cp ~/.m2/repository/org/apache/tinkerpop/gremlin-server/xx.yy.zz/gremlin-server-xx.yy.zz-distribution.zip* dev/xx.yy.zz`
  +.. `cp ~/.m2/repository/org/apache/tinkerpop/tinkerpop/xx.yy.zz/tinkerpop-xx.yy.zz-source-release.zip* dev/xx.yy.zz`
  +.. `cd dev/xx.yy.zz`
   .. 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"`
  +.. `cd ..; svn add xx.yy.zz/; svn ci -m "TinkerPop xx.yy.zz release"`
   . Execute `bin/validate-distribution.sh` and any other relevant testing.
  -. `git tag -a -m "TinkerPop x.y.z release" x.y.z` and `git push --tags`
  +. `git tag -a -m "TinkerPop xx.yy.zz release" xx.yy.zz` and `git push --tags`
   . 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"
   . Prepare Git administration tasks (apply the following steps as needed per release branch):
   .. Make the appropriate branching changes as required by the release and bump the version to `SNAPSHOT` with
   `mvn versions:set -DnewVersion=xx.yy.zz-SNAPSHOT -DgenerateBackupPoms=false`.
  -.. `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`
  -.. `mvn deploy -DskipTests` - deploy the new `SNAPSHOT`
  +.. `mvn clean install` - need to build first so that the right version of the console is used with `bin/publish-docs.sh`
  +.. `mvn deploy` - deploy the new `SNAPSHOT`
   .. `bin/process-docs.sh` and validate the generated `SNAPSHOT` documentation locally
   .. `bin/publish-docs.sh <username>` to publish the `SNAPSHOT` docs which enables the README to work properly.
   .. Update the links in the `README.asciidoc` to point at the `SNAPSHOT` version.
  +.. Commit and push the `SNAPSHOT` changes to git
   . Submit for `[VOTE]` at `dev@tinkerpop.apache.org` (see email template below)
   . *Wait for vote acceptance* (72 hours)
   
  
positive.code: .. `mvn verify -DskipIntegrationTests=false -DincludeNeo4j`
  .. `mvn verify -DskipPerformanceTests=false`
  . `bin/publish-docs.sh <username>` - note that under a release candidate the documentation is published as SNAPSHOT
  . `mvn versions:set -DnewVersion=x.y.z -DgenerateBackupPoms=false` to update the project files to reference a 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`
  . `mvn versions:set -DnewVersion=x.y.z-SNAPSHOT -DgenerateBackupPoms=false` to go back to SNAPSHOT
  . `git commit -a -m "Returned to x.y.z-SNAPSHOT"` and `git push`
  . Announce the release candidate to `dev` mailing list and await feedback
  . Repeat as required or proceed to the next phase
  
  
negative.code: Example `[VOTE]` email:
  
  ```
  [VOTE] TinkerPop xx.yy.zz Release
  
  Hello,
  
  The release artifacts can be found at this location:
  	https://dist.apache.org/repos/dist/dev/incubator/tinkerpop/xx.yy.zz/
  
  The source distribution is provided by:
  	apache-tinkerpop-xx.yy.zz-src.zip
  
  Two binary distributions are provided for user convenience:
  	apache-gremlin-console-xx.yy.zz-bin.zip
  	apache-gremlin-server-xx.yy.zz-bin.zip
  
  The online docs can be found here:
  	http://tinkerpop.apache.org/docs/xx.yy.zz/reference/ (user docs)
  	http://tinkerpop.apache.org/docs/xx.yy.zz/upgrade/ (upgrade docs)
  	http://tinkerpop.apache.org/javadocs/xx.yy.zz/core/ (core javadoc)
  	http://tinkerpop.apache.org/javadocs/xx.yy.zz/full/ (full javadoc)
  
  The tag in Apache Git can be found here:
  	https://git-wip-us.apache.org/repos/asf?p=incubator-tinkerpop.git;...
  