tinkerpop-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jorg...@apache.org
Subject [17/50] [abbrv] tinkerpop git commit: The tp31 branch is no longer maintained CTR
Date Wed, 20 Sep 2017 10:32:24 GMT
The tp31 branch is no longer maintained CTR


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

Branch: refs/heads/TINKERPOP-1730
Commit: f96017ba9116b79dee283ef0d6dd960665364000
Parents: 63191ae
Author: Stephen Mallette <spmva@genoprime.com>
Authored: Wed Sep 13 09:06:21 2017 -0400
Committer: Stephen Mallette <spmva@genoprime.com>
Committed: Wed Sep 13 09:06:21 2017 -0400

----------------------------------------------------------------------
 docs/src/dev/developer/for-committers.asciidoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/tinkerpop/blob/f96017ba/docs/src/dev/developer/for-committers.asciidoc
----------------------------------------------------------------------
diff --git a/docs/src/dev/developer/for-committers.asciidoc b/docs/src/dev/developer/for-committers.asciidoc
index 3593056..b812a01 100644
--- a/docs/src/dev/developer/for-committers.asciidoc
+++ b/docs/src/dev/developer/for-committers.asciidoc
@@ -67,12 +67,12 @@ Branches
 TinkerPop has several release branches:
 
 * `tp30` - 3.0.x (no longer maintained)
-* `tp31` - 3.1.x (bug fixes and documentation updates only)
+* `tp31` - 3.1.x (no longer maintained)
 * `tp32` - 3.2.x (bug fixes and documentation updates only)
 * `master` - 3.3.x
 
-Changes to `tp31` should merge to `tp32`, and changes to `tp32` should merge to `master`.
Please read more about this
-process in the <<pull-requests, Pull Requests>> section.
+Changes to `tp32` should merge to `master`. Please read more about this process in the <<pull-requests,
Pull Requests>>
+section.
 
 Other branches may be created for collaborating on features or for RFC's that other developers
may want to inspect.
 It is suggested that the JIRA issue ID be used as the prefix, since that triggers certain
automation, and it provides a


Mime
View raw message