bigtop-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c..@apache.org
Subject bigtop git commit: BIGTOP-2158. Update README.md to reflect the acceptance of CTR model
Date Tue, 24 Nov 2015 20:22:50 GMT
Repository: bigtop
Updated Branches:
  refs/heads/master 5545eb599 -> 5d7b6e072


BIGTOP-2158. Update README.md to reflect the acceptance of CTR model


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

Branch: refs/heads/master
Commit: 5d7b6e07223607f384b5092e61a682e65abab707
Parents: 5545eb5
Author: Konstantin Boudnik <cos@apache.org>
Authored: Tue Nov 24 12:21:57 2015 -0800
Committer: Konstantin Boudnik <cos@apache.org>
Committed: Tue Nov 24 12:22:36 2015 -0800

----------------------------------------------------------------------
 README.md | 17 ++++++++---------
 1 file changed, 8 insertions(+), 9 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/bigtop/blob/5d7b6e07/README.md
----------------------------------------------------------------------
diff --git a/README.md b/README.md
index 97c539b..61502d2 100644
--- a/README.md
+++ b/README.md
@@ -55,13 +55,11 @@ 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
-===============
+CTR model
+=========
 
-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:
+Bigtop supports Commit-Then-Review model of development. 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
@@ -70,12 +68,13 @@ whichever comes first. The following rules will be used for the CTR process:
     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
+    http://ci.bigtop.apache.org/view/Bigtop-trunk/ (Bigtop-trunk-packages 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.
+    community feedback before it gets committed unless it has an explicit +1
+    from another committer
   * 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


Mime
View raw message