Author: buildbot
Date: Wed Mar 19 17:34:27 2014
New Revision: 902360
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/bylaws.html
Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Mar 19 17:34:27 2014
@@ -1 +1 @@
-1579300
+1579304
Modified: websites/staging/accumulo/trunk/content/bylaws.html
==============================================================================
--- websites/staging/accumulo/trunk/content/bylaws.html (original)
+++ websites/staging/accumulo/trunk/content/bylaws.html Wed Mar 19 17:34:27 2014
@@ -135,6 +135,17 @@ stability, and robustness of both code a
<p>A PMC member is considered emeritus, meaning inactive, by his or her own
declaration or by not contributing in any form to the project for over six
months. Emeritus members will be recognized by the PMC on the Accumulo web
page, in honor of their past contributions. Emeritus members retain all voting
and commit rights associated with their former designation and can move
themselves out of emeritus status by sending an announcement of their return to
the developer mailing list. It will be the returning member's responsibility to
update his/her status on the web page accordingly.</p>
<p>The chair of the PMC is appointed by the ASF board. The chair is an office
holder of the Apache Software Foundation (Vice President, Apache Accumulo) and
has primary responsibility to the board for the management of the projects
within the scope of the Accumulo PMC. The chair reports to the board quarterly
on developments within the Accumulo project.</p>
<p>When the current chair of the PMC resigns, the PMC votes to recommend a new
chair using consensus approval, but the decision must be ratified by the Apache
board.</p>
+<h2 id="release-manager">Release Manager</h2>
+<p>The <a href="https://www.apache.org/dev/release-publishing.html";>ASF
release process</a> defines the <a
href="https://www.apache.org/dev/release-publishing.html#release_manager";>release
manager</a> as an individual responsible for shepherding a new project
release. Any committer may serve as a release manager. The release manager for
a release is chosen as part of the release plan.</p>
+<p>At a minimum, a release manager is responsible for packaging a release
candidate for a vote and signing and publishing an approved release candidate.
An Accumulo release manager is also expected to:</p>
+<ul>
+<li>guide whether changes after feature freeze or code freeze should be
included in the release</li>
+<li>ensure that required release testing is being conducted</li>
+<li>track whether the release is on target for its expected release date</li>
+<li>determine if a re-plan may be needed and, if so, call a vote</li>
+<li>call votes on release candidates</li>
+</ul>
+<p><a href="http://accumulo.apache.org/releasing.html";>Release guidelines</a>
and <a href="http://accumulo.apache.org/releasing.html";>details on the
mechanics of creating an Accumulo release</a> are available on the Accumulo
project site.</p>
<h1 id="decision-making">Decision Making</h1>
<p>Within the Accumulo project, different types of decisions require different
forms of approval. For example, the previous section describes several
decisions which require 'consensus approval'. This section defines how voting
is performed, the types of approvals, and which types of decision require which
type of approval.</p>
<h2 id="voting">Voting</h2>
@@ -184,7 +195,7 @@ stability, and robustness of both code a
<td>Active committers</td>
<td>1</td>
<tr><td>Release Plan</td>
- <td>Defines the timetable and actions for a release. The plan also
nominates a Release Manager.</td>
+ <td>Defines the timetable and actions for an upcoming release. The plan
also nominates a Release Manager.</td>
<td>Lazy approval, moving to majority approval upon veto</td>
<td>Active committers</td>
<td>3</td>
@@ -194,7 +205,7 @@ stability, and robustness of both code a
<td>Active committers</td>
<td>3</td>
<tr><td>Product Release</td>
- <td>When a release of one of the project's products is ready, a vote is
required to accept the release as an official release of the project.</td>
+ <td>Accepts or rejects a release candidate as an official release of the
project.</td>
<td>Majority approval</td>
<td>Active PMC members</td>
<td>3</td>
