Author: buildbot
Date: Mon Sep 17 14:30:45 2012
New Revision: 832261
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/governance/releasing.html
Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Sep 17 14:30:45 2012
@@ -1 +1 @@
-1376052
+1386630
Modified: websites/staging/accumulo/trunk/content/governance/releasing.html
==============================================================================
--- websites/staging/accumulo/trunk/content/governance/releasing.html (original)
+++ websites/staging/accumulo/trunk/content/governance/releasing.html Mon Sep
17 14:30:45 2012
@@ -105,6 +105,7 @@
</ul>
</li>
<li>Wrap up any standing documentation endeavors, whether or not there are
tickets for them.</li>
+<li>Analyze API changes since last major release and ensure there are no
changes that will cause pain for users.</li>
<li>Test the branch as per our testing criteria.</li>
<li>Once testing is deemed successful and release documentation is complete,
move on to Releasing.</li>
</ol>
@@ -119,6 +120,7 @@
<ol>
<li>All JUnit tests must pass. This should be a requirement of any patch so
it should never be an issue of the codebase.</li>
<li>All functional tests must complete successfully.</li>
+<li>Analyze output of static analysis tools like Findbugs and PMD.</li>
<li>Two 24-hour periods of the randomwalk LongClean test with and without
agitation need to be run successfully on a cluster.</li>
<li>Two 24-hour periods of continuous ingest with and without agitation need
to be validated successfully on a cluster.</li>
<li>Two 72-hour periods of continuous ingest with and without agitation on a
cluster. No validation is necessary but the cluster should be checked to ensure
it is still functional.</li>
