[
https://issues.apache.org/jira/browse/HADOOP-8248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HADOOP-8248:
--------------------------------
Attachment: proposed-bylaw-change.txt
Here is the proposed change as a patch. Copy-pasting inline for easy reading:
{code}
<li> <strong>Code Change</strong>
<p>A change made to a codebase of the project and committed
by a committer. This includes source code, documentation, website
content, etc.</p>
<p>Such changes require lazy consensus of active committers,
but with a minimum of one +1. The +1 must be provided by a committer
who is not a primary author of the patch.
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>
<p>In the case of trivial changes, a committer may commit after a
non-binding +1 vote from a contributor or the issue reporter. The
definition of what constitutes a trivial change is subject to the
best judgment of the committer, but should generally be limited
to changes such as: documentation fixes, spelling mistakes, log
message changes, or the addition of new test code.</p>
<p>In the case of feature branches, the creator of the branch
may elect to forego this review-then-commit policy on that branch,
with the understanding that three committers must provide a +1
vote before its eventual merge as described above.</p>
</li>
{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: 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
