anchor.diff:  .. 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.
  
positive.code: 
  A positive vote for a particular release from the TinkerPop PMC is required to move to the following phase.
  
  . `mvn clean install`
  .. `mvn verify -DskipIntegrationTests=false -DincludeNeo4j`
  .. `mvn verify -DskipPerformanceTests=false`
  . Perform manual tests:
  .. Execute `:remote connect conf/remote.yaml` and send some requests to a running Gremlin Server instance.
  .. Execute `:?` to display the help in the Console.
  . Update `CHANGELOG.asciidoc`:
  .. Update the release date
  .. Generate the JIRA release notes report for the current version and append them to the `CHANGELOG.asciidoc`
  .. Organize "breaking" changes to be clearly marked (use JIRA and the "breaking" label to identify those)
  . Update "upgrade documentation":
  .. Update the release date.
  
negative.code: . `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`
  . `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
  . `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`
  