anchor.diff:  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 - the easiest way to is to view the `CHANGELOG.asciidoc` to be sure that it produces a link in the
  -GitHub viewer. 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.
  +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`.
  
positive.code: 	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:
  	https://github.com/apache/tinkerpop/tree/xx.yy.zz
  
  The release notes are available here:
  
negative.code: . Update "upgrade documentation":
  .. Update the release date.
  .. Update the link to `CHANGELOG.asciidoc` - this link may already be correct but will not exist until the repository is tagged.
  . `mvn versions:set -DnewVersion=xx.yy.zz -DgenerateBackupPoms=false` to update project files to reference the non-SNAPSHOT version
  . `mvn clean install -DskipTests` to update GLV versions
  .. Review `Gremlin.Net.csproj`, `Gremlin.Net.Template.csproj` and `Gremlin.Net.Template.nuspec` in `gremlin-dotnet`
  