tinkerpop-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From spmalle...@apache.org
Subject [3/4] incubator-tinkerpop git commit: Update release docs based on new "upgrade docs".
Date Tue, 13 Oct 2015 14:11:54 GMT
Update release docs based on new "upgrade docs".


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

Branch: refs/heads/tp30
Commit: 792c083eead00b423a9dfc4d7731a9aeba0a0efa
Parents: 9345dba
Author: Stephen Mallette <spmva@genoprime.com>
Authored: Tue Oct 13 08:41:47 2015 -0400
Committer: Stephen Mallette <spmva@genoprime.com>
Committed: Tue Oct 13 08:41:47 2015 -0400

----------------------------------------------------------------------
 RELEASE.asciidoc | 24 ++++++++++++++++++++++--
 1 file changed, 22 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/blob/792c083e/RELEASE.asciidoc
----------------------------------------------------------------------
diff --git a/RELEASE.asciidoc b/RELEASE.asciidoc
index 2947d2b..b6211bd 100644
--- a/RELEASE.asciidoc
+++ b/RELEASE.asciidoc
@@ -17,17 +17,34 @@ limitations under the License.
 Release Process
 ---------------
 
-This document describes the steps required to release a version of TinkerPop.  The process
is multi-phased and can therefore take several weeks to complete given the time needed for
Apache voting and community feedback.  Once a release point has been identified, the following
phases represent the flow of "release":
+This document describes the steps required to release a version of TinkerPop.  The process
is multi-phased and can
+therefore take several weeks to complete given the time needed for Apache voting and community
feedback.  Once a
+release point has been identified, the following phases represent the flow of "release":
 
+* Pre-flight check.
 * Optionally, produce a release candidate for community feedback.
 * Submit the official release for PMC vote.
 * Submit the official release for Incubator vote.
 * Release and promote.
 
+Pre-flight Check
+~~~~~~~~~~~~~~~~
+
+The "pre-flight check" is a list of things performed during the week before the schedule
day to release.  These checks
+will help to ensure that that release day goes smoothly by identifying problems up early
and communicating with
+other members of the community.
+
+. Seven days before release, issue an email to the dev mailing list to remind the community
of the pending release.
+.. Note any important issues open in JIRA in that post.
+.. Request review and update of the "upgrade documentation" and CHANGELOG.
+. At some point during the week, review LICENSE and NOTICE files to make sure that no changes
are needed.
+
 Release Candidate
 ~~~~~~~~~~~~~~~~~
 
-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.
+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.
 
 . `mvn clean install -DincludeNeo4j`
 .. `mvn verify -DskipIntegrationTests=false -DincludeNeo4j`
@@ -58,6 +75,9 @@ A positive vote for a particular release from the TinkerPop PMC is required
to m
 .. Update the release date
 .. Generate the JIRA release notes report for the current version and append them to the
`CHANGELOG.asciidoc`
 .. Organize "breaking" changes to be clearly marked (use JIRA and the "breaking" label to
identify those)
+. Update "upgrade documentation":
+.. Update the release date.
+.. Update the link to CHANGELOG.asciidoc
 . `mvn versions:set -DnewVersion=x.y.z -DgenerateBackupPoms=false` to update project files
to reference the non-SNAPSHOT version
 . `git diff` and review the updated files (expect all `pom.xml` files and this README)
 . `git commit -a -m "TinkerPop x.y.z release"` and `git push`


Mime
View raw message