Author: bhavanki
Date: Wed Mar 19 17:43:34 2014
New Revision: 1579315
URL: http://svn.apache.org/r1579315
Log:
Add release plan section, one more RM responsibility
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=1579315&r1=1579314&r2=1579315&view=diff
==============================================================================
--- accumulo/site/trunk/content/bylaws.mdtext (original)
+++ accumulo/site/trunk/content/bylaws.mdtext Wed Mar 19 17:43:34 2014
@@ -95,6 +95,7 @@ At a minimum, a release manager is respo
* 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
+* adjust release plan dates to reflect the latest estimates
* determine if a re-plan may be needed and, if so, call a vote
* call votes on release candidates
@@ -202,4 +203,21 @@ No other voting actions are defined. If
For the purposes of the "Adoption of New Codebase" action, the Accumulo
codebase is defined as the Accumulo site content, primary project code, and all
contributed code ("contribs") as they exist in their respective repositories.
Adoption of a new codebase generally refers to the creation of a new contrib
repository, but could cover, for example, a rework of the project site, or
merging a contrib project into the primary codebase.
-Voting actions for the removal of a committer or PMC member are intentionally
not defined. According to ASF rules, [committer status never
expires](http://www.apache.org/dev/committers.html#committer-set-term) and [the
ASF board removes PMC members](http://www.apache.org/dev/pmc.html#pmc-removal).
\ No newline at end of file
+Voting actions for the removal of a committer or PMC member are intentionally
not defined. According to ASF rules, [committer status never
expires](http://www.apache.org/dev/committers.html#committer-set-term) and [the
ASF board removes PMC members](http://www.apache.org/dev/pmc.html#pmc-removal).
+
+# Release Plans
+
+The approval of a release plan begins the process of creating a new project
release. The process ends when a release candidate is approved.
+
+An Accumulo release plan consists of at least the following:
+
+* a version number
+* a feature freeze date
+* a code freeze date
+* a release date
+* the choice of a release manager
+
+After feature freeze, new features should not be accepted for the release.
After code freeze, only critical fixes should be accepted for the release. The
release manager guides the decision on accepting changes.
+
+All dates in a plan are estimates, as unforeseen issues may require delays.
The release manager may adjust dates as needed. In serious circumstances, the
release manager may opt to call a re-plan vote.
+
