anchor.diff:  	https://tinkerpop.apache.org/dotnetdocs/xx.yy.zz/ (.NET API docs)
   	https://tinkerpop.apache.org/jsdocs/xx.yy.zz/ (Javascript API docs)
   
  -The tag in Apache Git can be found here:
  +The Git tag can be found here:
   	https://github.com/apache/tinkerpop/tree/xx.yy.zz
   
   The release notes are available here:
  
positive.code: . `cd release; svn add xx.yy.zz/; svn ci -m "TinkerPop xx.yy.zz release"`
  . Wait for Apache Sonatype to sync the artifacts to Maven Central at (link:https://repo1.maven.org/maven2/org/apache/tinkerpop/tinkerpop/[https://repo1.maven.org/maven2/org/apache/tinkerpop/tinkerpop/]).
  . Report the release through link:https://reporter.apache.org/addrelease.html?tinkerpop[reporter.apache.org] (an email reminder should arrive shortly following the svn command above to do the release)
  . Update the `site/downloads.html` - provide the contents for the modal that pops up from the "contributors" link.
  . Wait for zip distributions to sync to the Apache mirrors (i.e ensure the download links work from a mirror).
  . `bin/publish-home.sh <username>` to publish the updated web site with new releases.
  . Execute `bin/update-current-docs.sh <username>` to migrate to the latest documentation set for `/current`.
  
negative.code: validity into question.
  . Update `CHANGELOG.asciidoc`:
  .. Update the release date - the release date is the date of the vote. Double check the header to be sure that it is
  formatted properly - specifically, ensure that there is an asciidoc anchor of the format `[[release-x-y-z]]` above the
  version/date header. The release date is the intended day of the vote and not necessarily when it happens (usually
  falls on a Monday given the code freeze pattern that starts a week prior on a Friday). The release date for all
  versions should be the same as the first release of the set even if the release vote does not begin on the same day.
  In other words if 3.2.x has a vote date of "October, 1 2018" then 3.3.x should also have that date even if the vote
  thread for 3.3.x doesn't start until the day after.
  .. 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:
  `project = TINKERPOP and status = Closed AND fixVersion = 3.2.0 ORDER BY type, Id ASC`.
  