Return-Path: 
 <common-issues-return-29629-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 5C42095B4
	for <apmail-hadoop-common-issues-archive@minotaur.apache.org>;
 Mon,  9 Apr 2012 20:53:39 +0000 (UTC)
Received: (qmail 15937 invoked by uid 500); 9 Apr 2012 20:53:39 -0000
Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org
Received: (qmail 15903 invoked by uid 500); 9 Apr 2012 20:53:39 -0000
Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-issues@hadoop.apache.org>
List-Id: <common-issues.hadoop.apache.org>
Reply-To: common-issues@hadoop.apache.org
Delivered-To: mailing list common-issues@hadoop.apache.org
Received: (qmail 15895 invoked by uid 99); 9 Apr 2012 20:53:39 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Apr 2012 20:53:39 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Apr 2012 20:53:37 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id E15FA362283
	for <common-issues@hadoop.apache.org>; Mon,  9 Apr 2012 20:53:17 +0000 (UTC)
Date: Mon, 9 Apr 2012 20:53:17 +0000 (UTC)
From: "Tsz Wo (Nicholas), SZE (Updated) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1260606424.4694.1334004797924.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <957502829.15310.1333588398678.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HADOOP-8248) Clarify bylaws about
 review-then-commit policy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/HADOOP-8248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz Wo (Nicholas), SZE updated HADOOP-8248:
-------------------------------------------

    Attachment: c8248_20120409.patch

c8248_20120409.patch: my proposed change
{code}
Index: main/author/src/documentation/content/xdocs/bylaws.xml
===================================================================
--- main/author/src/documentation/content/xdocs/bylaws.xml	(revision 1311409)
+++ main/author/src/documentation/content/xdocs/bylaws.xml	(working copy)
@@ -244,10 +244,17 @@
             content, etc.</p>
 
             <p>Lazy consensus of active committers, but with a minimum of
-            one +1. The code can be committed after the first +1, unless
-            the code change represents a merge from a branch, in which case
-            three +1s are required.</p></li>
+            one +1. When the code change can be submitted by a patch, the code
+            can be committed after the first +1.  The +1 can be cast from a
+            reviewer who is not one of the authors of the patch. For
+            significant patches, the reviewer must be a committer.  Otherwise,
+            the reviewer can be any contributor.</p>
 
+            <p>When code change is both large and significant, it must be either
+            splitted into subtasks or first committed to a development branch.
+            When the code change represents a merge from a branch, +1s from
+            three committers who are not the authors are required.</p></li>
+
          <li> <strong>Release Plan</strong>
 
             <p>Defines the timetable and actions for a release. The plan also
{code}
                
> Clarify bylaws about review-then-commit policy
> ----------------------------------------------
>
>                 Key: HADOOP-8248
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8248
>             Project: Hadoop Common
>          Issue Type: Task
>            Reporter: Todd Lipcon
>         Attachments: c8248_20120409.patch, proposed-bylaw-change.txt
>
>
> As discussed on the mailing list (thread "Requirements for patch review" 4/4/2012) we should clarify the bylaws with respect to the review-then-commit policy. This JIRA is to agree on the proposed change.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira