Repository: tinkerpop Updated Branches: refs/heads/tp32 75b3d7429 -> 7c954e90d
Add a note about the version change for Gremlin.Net CTR Project: http://git-wip-us.apache.org/repos/asf/tinkerpop/repo Commit: http://git-wip-us.apache.org/repos/asf/tinkerpop/commit/7c954e90 Tree: http://git-wip-us.apache.org/repos/asf/tinkerpop/tree/7c954e90 Diff: http://git-wip-us.apache.org/repos/asf/tinkerpop/diff/7c954e90 Branch: refs/heads/tp32 Commit: 7c954e90db923caa366b7de8052a420370a0258c Parents: 75b3d74 Author: Stephen Mallette <sp...@genoprime.com> Authored: Mon Aug 28 11:27:16 2017 -0400 Committer: Stephen Mallette <sp...@genoprime.com> Committed: Mon Aug 28 11:27:16 2017 -0400 ---------------------------------------------------------------------- docs/src/dev/developer/release.asciidoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/tinkerpop/blob/7c954e90/docs/src/dev/developer/release.asciidoc ---------------------------------------------------------------------- diff --git a/docs/src/dev/developer/release.asciidoc b/docs/src/dev/developer/release.asciidoc index aa321ca..22d1e2b 100644 --- a/docs/src/dev/developer/release.asciidoc +++ b/docs/src/dev/developer/release.asciidoc @@ -191,8 +191,9 @@ current release was under development as this new release will have those change . `mvn versions:set -DnewVersion=xx.yy.zz -DgenerateBackupPoms=false` to update project files to reference the non-SNAPSHOT version . `pushd gremlin-console/bin; ln -fs ../target/apache-tinkerpop-gremlin-console-xx.yy.zz-standalone/bin/gremlin.sh gremlin.sh; popd` . `git diff` and review the updated files -. `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` +.. This step should update the Gremlin.Net project file with the newly bumped version. +. `git commit -a -m "TinkerPop xx.yy.zz release"` and push . `bin/process-docs.sh` and validate the generated documentation locally. Don't rely on "BUILD SUCCESS" - scroll up through logs to ensure there were no errors and view the HTML directly. Code blocks that did not execute properly have a gray background and do not show the results of the commands. . `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. Note that this step will be responsible
