Author: buildbot
Date: Fri Nov 8 16:28:39 2013
New Revision: 885895
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/git.html
Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Nov 8 16:28:39 2013
@@ -1 +1 @@
-1539515
+1540108
Modified: websites/staging/accumulo/trunk/content/git.html
==============================================================================
--- websites/staging/accumulo/trunk/content/git.html (original)
+++ websites/staging/accumulo/trunk/content/git.html Fri Nov 8 16:28:39 2013
@@ -257,6 +257,18 @@ name. It has been suggested to name the
Maven releases are named. In other words, the branch just created would be
named <code>1.4.4-snapshot</code> or similar.</p>
<h3 id="reviewing-contributor-changes">Reviewing contributor changes</h3>
+<p>It is always the responsibility of committers to determine that a patch is
+intended and able to be contributed. From the
+<a href="http://www.apache.org/dev/new-committers-guide.html#cla";>new
committer's guide</a>:
+"Please take care to ensure that patches are original works which have been
+clearly contributed to the ASF in public. In the case of any doubt (or when a
+contribution with a more complex history is presented) please consult your
+project PMC before committing it."</p>
+<p>Extra diligence may be necessary when code is contributed via a pull
request.
+Committers should verify that the contributor intended to submit the code as a
+Contribution under the <a
href="http://www.apache.org/licenses/LICENSE-2.0.txt";>Apache License</a>.
+When pulling the code, committers should also verify that the commits pulled
match the
+list of commits sent to the Accumulo dev list in the pull request.</p>
<p><strong>Patches</strong> -- Developers should use the following steps to
apply patches from
contributors:</p>
<ol>
