Author: bhavanki
Date: Wed Mar 19 17:34:21 2014
New Revision: 1579304
URL: http://svn.apache.org/r1579304
Log:
Add release manager section; update release vote descriptions
Modified:
accumulo/site/trunk/content/bylaws.mdtext
Modified: accumulo/site/trunk/content/bylaws.mdtext
URL:
http://svn.apache.org/viewvc/accumulo/site/trunk/content/bylaws.mdtext?rev=1579304&r1=1579303&r2=1579304&view=diff
==============================================================================
--- accumulo/site/trunk/content/bylaws.mdtext (original)
+++ accumulo/site/trunk/content/bylaws.mdtext Wed Mar 19 17:34:21 2014
@@ -86,6 +86,20 @@ The chair of the PMC is appointed by the
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.
+## Release Manager
+
+The [ASF release process](https://www.apache.org/dev/release-publishing.html)
defines the [release
manager](https://www.apache.org/dev/release-publishing.html#release_manager) 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.
+
+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:
+
+* guide whether changes after feature freeze or code freeze should be included
in the release
+* ensure that required release testing is being conducted
+* track whether the release is on target for its expected release date
+* determine if a re-plan may be needed and, if so, call a vote
+* call votes on release candidates
+
+[Release guidelines](http://accumulo.apache.org/releasing.html) and [details
on the mechanics of creating an Accumulo
release](http://accumulo.apache.org/releasing.html) are available on the
Accumulo project site.
+
# Decision Making
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.
@@ -148,7 +162,7 @@ This section describes the various actio
<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>
@@ -158,7 +172,7 @@ This section describes the various actio
<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>
