hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8248) Clarify bylaws about review-then-commit policy
Date Thu, 05 Apr 2012 20:54:24 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247658#comment-13247658
] 

Doug Cutting commented on HADOOP-8248:
--------------------------------------

Different projects do different things.  A lot of Apache projects are CTR; no explicit review
is required before any commit.  On Avro, if a patch doesn't get a review after a few days
we'll often say something like, "I'll commit this tomorrow unless someone objects".  So an
opportunity for review before commit is provided, but a review is not required.  But on Hadoop
a +1 from a committer who is not the patch author has always been required for significant
patches.
                
> 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: 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