tinkerpop-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From florianhockm...@apache.org
Subject [03/39] tinkerpop git commit: Updated dev docs for release candidates CTR
Date Mon, 05 Mar 2018 18:54:21 GMT
Updated dev docs for release candidates CTR

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

Branch: refs/heads/TINKERPOP-1897
Commit: 072f112df0faff4d8e78772e73c8b708e184a44b
Parents: 5b4bd00
Author: Stephen Mallette <spmva@genoprime.com>
Authored: Sat Feb 24 16:00:37 2018 -0500
Committer: Stephen Mallette <spmva@genoprime.com>
Committed: Sat Feb 24 16:00:37 2018 -0500

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

diff --git a/docs/src/dev/developer/release.asciidoc b/docs/src/dev/developer/release.asciidoc
index 44afe8f..fab9819 100644
--- a/docs/src/dev/developer/release.asciidoc
+++ b/docs/src/dev/developer/release.asciidoc
@@ -135,7 +135,8 @@ of the published documentation on the dev mailing list.
 A release candidate is an unofficial release that is represented by a tagged version in the
Git repository.  It is
 offered in cases where there is significant change in a particular version and the potential
for upgrades and problems
-might be high.
+might be high. Release candidates do not require a vote thread. Lazy consensus is acceptable
for confirming their
 . `mvn clean install -DincludeNeo4j`
 .. `mvn verify -DskipIntegrationTests=false -DincludeNeo4j`
@@ -153,6 +154,14 @@ might be high.
 . Announce the release candidate to `dev` mailing list and await feedback
 . Repeat as required or proceed to the next phase
+Note that release candidates need not require the release of all artifacts. For example,
if the risk is with one
+particular GLV, then a release candidate can be prepared of just that particular artifact.
In those cases, a tag on
+the commit that represents the release candidate is sufficient and does not necessarily require
that the versions
+be bumped to reflect the actual "-rc" version. In other words, if preparing a release candidate
for .NET, then there
+is no need to go through the processing of bumping versions in Java artifacts and all GLVs.
Nor is it necessary to
+alter the version of .NET to include the release candidate versioning. It can simply be altered
locally by the
+release manager and deployed.
 == PMC Vote
 This section describes the process that process that prepares a release for VOTE by the community.
If there are multiple

View raw message