incubator-tinkerpop git commit: Update release docs regarding README and staging "next release".

[sp...@apache.org]

Repository: incubator-tinkerpop
Updated Branches:
  refs/heads/master 8d04917f8 -> 3b69e269e


Update release docs regarding README and staging "next release".


Project: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/commit/3b69e269
Tree: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/tree/3b69e269
Diff: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/diff/3b69e269

Branch: refs/heads/master
Commit: 3b69e269e49ef8b52b65bc7eb105301b886a74e4
Parents: 8d04917
Author: Stephen Mallette <sp...@genoprime.com>
Authored: Mon Nov 23 15:18:33 2015 -0500
Committer: Stephen Mallette <sp...@genoprime.com>
Committed: Mon Nov 23 15:18:33 2015 -0500

----------------------------------------------------------------------
 docs/src/dev/developer/release.asciidoc | 9 +++++++++
 1 file changed, 9 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/blob/3b69e269/docs/src/dev/developer/release.asciidoc
----------------------------------------------------------------------
diff --git a/docs/src/dev/developer/release.asciidoc b/docs/src/dev/developer/release.asciidoc
index a5ddcc8..6d1f141 100644
--- a/docs/src/dev/developer/release.asciidoc
+++ b/docs/src/dev/developer/release.asciidoc
@@ -88,6 +88,7 @@ A positive vote for a particular release from the TinkerPop PMC is required to m
 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 the links in the `README.asciidoc` to point at the latest version.
 . Update `CHANGELOG.asciidoc`:
 .. Update the release date
 .. Generate the JIRA release notes report for the current version and append them to the `CHANGELOG.asciidoc`.
@@ -123,6 +124,14 @@ handled document generation and this step now merely needs to upload what was ge
 . 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`
+.. `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.
 . Submit for `[VOTE]` at `dev@tinkerpop.incubator.apache.org` (see email template below)
 . *Wait for vote acceptance* (72 hours)