hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8248) Clarify bylaws about review-then-commit policy
Date Mon, 09 Apr 2012 20:53:17 GMT

     [ 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

        

Mime
View raw message