accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r902363 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Date Wed, 19 Mar 2014 17:43:40 GMT
Author: buildbot
Date: Wed Mar 19 17:43:40 2014
New Revision: 902363

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:43:40 2014
@@ -1 +1 @@
-1579304
+1579315

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:43:40 2014
@@ -142,6 +142,7 @@ stability, and robustness of both code a
 <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>adjust release plan dates to reflect the latest estimates</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>
@@ -234,6 +235,18 @@ stability, and robustness of both code a
 <p>No other voting actions are defined. If a new one is found to be needed, it should
be added to these bylaws.</p>
 <p>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.</p>
 <p>Voting actions for the removal of a committer or PMC member are intentionally not
defined. According to ASF rules, <a href="http://www.apache.org/dev/committers.html#committer-set-term">committer
status never expires</a> and <a href="http://www.apache.org/dev/pmc.html#pmc-removal">the
ASF board removes PMC members</a>.</p>
+<h1 id="release-plans">Release Plans</h1>
+<p>The approval of a release plan begins the process of creating a new project release.
The process ends when a release candidate is approved.</p>
+<p>An Accumulo release plan consists of at least the following:</p>
+<ul>
+<li>a version number</li>
+<li>a feature freeze date</li>
+<li>a code freeze date</li>
+<li>a release date</li>
+<li>the choice of a release manager</li>
+</ul>
+<p>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.</p>
+<p>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.</p>
   </div>
 
   <div id="footer">



Mime
View raw message