You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tinkerpop.apache.org by dk...@apache.org on 2015/10/13 23:23:03 UTC
[10/12] incubator-tinkerpop git commit: Tweaked CONTRIBUTING to
discuss external pull requests and RTC.
Tweaked CONTRIBUTING to discuss external pull requests and RTC.
Project: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/commit/383e86ed
Tree: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/tree/383e86ed
Diff: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/diff/383e86ed
Branch: refs/heads/TINKERPOP3-319
Commit: 383e86ed06b9f1c994571a32ba85ae2bd75b1857
Parents: c9b17d3
Author: Stephen Mallette <sp...@genoprime.com>
Authored: Tue Oct 13 12:03:39 2015 -0400
Committer: Stephen Mallette <sp...@genoprime.com>
Committed: Tue Oct 13 12:03:39 2015 -0400
----------------------------------------------------------------------
CONTRIBUTING.asciidoc | 5 +++++
1 file changed, 5 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/blob/383e86ed/CONTRIBUTING.asciidoc
----------------------------------------------------------------------
diff --git a/CONTRIBUTING.asciidoc b/CONTRIBUTING.asciidoc
index f6f085b..462a6d5 100644
--- a/CONTRIBUTING.asciidoc
+++ b/CONTRIBUTING.asciidoc
@@ -206,6 +206,11 @@ committer wanting to put code into a release branch.
** If there is a higher version release branch that requires your fix (e.g. `3.0.z` fix going to a `3.y.z` release), be sure to merge to that release branch as well.
* Be conscious of deleting your branch if it is no longer going to be used so stale branches don't pollute the repository.
+NOTE: These steps also generally apply to external pull requests from those who are not official Apache committers. In
+this case, the person responsible for the merge after voting is typically the first person available
+who is knowledgeable in the area that the pull request affects. Any additional coordination on merging can be handled
+via the pull request comment system.
+
The following exceptions to the RTC (review-then-commit) model presented above are itemized below. It is up to the
committer to self-regulate as the itemization below is not complete and only hints and the types of commits that do not
require a review.