You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bigtop.apache.org by co...@apache.org on 2015/09/25 08:45:17 UTC
bigtop git commit: BIGTOP-2069. Update README.md to reflect CTR trial
Repository: bigtop
Updated Branches:
refs/heads/master 601ebce01 -> e994b24ac
BIGTOP-2069. Update README.md to reflect CTR trial
Project: http://git-wip-us.apache.org/repos/asf/bigtop/repo
Commit: http://git-wip-us.apache.org/repos/asf/bigtop/commit/e994b24a
Tree: http://git-wip-us.apache.org/repos/asf/bigtop/tree/e994b24a
Diff: http://git-wip-us.apache.org/repos/asf/bigtop/diff/e994b24a
Branch: refs/heads/master
Commit: e994b24ac945b762c8656265f65d2aca66a2e7f3
Parents: 601ebce
Author: Konstantin Boudnik <co...@apache.org>
Authored: Thu Sep 24 23:44:56 2015 -0700
Committer: Konstantin Boudnik <co...@apache.org>
Committed: Thu Sep 24 23:44:56 2015 -0700
----------------------------------------------------------------------
README.md | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/bigtop/blob/e994b24a/README.md
----------------------------------------------------------------------
diff --git a/README.md b/README.md
index 6342f92..0460fe8 100644
--- a/README.md
+++ b/README.md
@@ -55,6 +55,31 @@ There are lots of ways to contribute. People with different expertise can help
Also, opening [JIRA's](https://issues.apache.org/jira/browse/BIGTOP) and getting started by posting on the mailing list is helpful.
+CTR model trial
+===============
+
+As discussed on the dev@ list (http://bit.ly/1gLeArc) we are going into a trial
+period of CTR model for Bigtop project. The trial will go into effect until
+Dec, 5th, 2015 or for two months since the master CI disk space issues are resolve,
+whichever comes first. The following rules will be used for the CTR process:
+ * a committer can go ahead and commit the patch without mandatory review if
+ felt confident in its quality (e.g. reasonable testing has been done
+ locally; all compilations pass; RAT check is passed; the patch follows
+ coding guidelines)
+ * a committer is encouraged to seek peer-review and/or advice before hand if
+ there're doubts in the approach taken, design decision, or implementation
+ details
+ * a committer should keep an eye on the official CI builds at
+ http://ci.bigtop.apache.org:8080/view/Bigtop-trunk/ (Docker-Bigtop-*
+ builds) to make sure that committed changes haven't break anything. In
+ which case the committer should take a timely effort to resolve the issues
+ and unblock the others in the community
+ * any non-document patch is required to be opened for at least 24 hours for
+ review before it gets committed unless it has other committer's +1.
+ * any non-document patch needs to address all the comment and reach consensus
+ before it gets committed without a +1 from other committers
+ * there's no changes in the JIRA process, except as specified above
+
What do people use Apache Bigtop for?
==============================