accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r903472 - in /websites/staging/accumulo/trunk/content: ./ governance/releasing.html
Date Tue, 25 Mar 2014 07:29:22 GMT
Author: buildbot
Date: Tue Mar 25 07:29:21 2014
New Revision: 903472

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 Tue Mar 25 07:29:21 2014
@@ -1 +1 @@
-1579959
+1581267

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 Tue Mar 25 07:29:21
2014
@@ -140,21 +140,21 @@
 </li>
 </ol>
 <h3 id="cluster-based">Cluster based</h3>
-<p>The following tests require a Hadoop cluster running a minimum of HDFS, MapReduce,
and ZooKeeper. The cluster MAY have any number of worker nodes; it can even be a single node
in psuedo-distributed mode. A cluster with multiple tablet servers SHOULD be used so that
more of the code base will be exercised. For the purposes of release testing, you should note
the number of nodes and versions used. See the Releasing section for more details.</p>
+<p>The following tests require a Hadoop cluster running a minimum of HDFS, MapReduce,
and ZooKeeper. The cluster MAY have any number of worker nodes; it can even be a single node
in pseudo-distributed mode. A cluster with multiple tablet servers SHOULD be used so that
more of the code base will be exercised. For the purposes of release testing, you should note
the number of nodes and versions used. See the Releasing section for more details.</p>
 <ol>
 <li>For versions prior to 1.6, all functional tests must complete successfully.<ul>
 <li>See $ACCUMULO_HOME/test/system/auto/README for details on running the functional
tests.</li>
 </ul>
 </li>
-<li>Two 24-hour periods of the randomwalk LongClean test with and without agitation
need to be run successfully.<ul>
+<li>Two 24-hour periods of the LongClean module of the RandomWalk test need to be run
successfully. One of them must use agitation and the other should not.<ul>
 <li>See $ACCUMULO_HOME/test/system/randomwalk/README for details on running the LongClean
module.</li>
 </ul>
 </li>
-<li>Two 24-hour periods of continuous ingest with and without agitation need to be
validated successfully.<ul>
-<li>See $ACCUMULO_HOME/test/system/continuous/README for details on running and verifying
the continous ingest test.</li>
+<li>Two 24-hour periods of the continuous ingest test must be validated successfully.
One test period must use agitation and the other should not.<ul>
+<li>See $ACCUMULO_HOME/test/system/continuous/README for details on running and verifying
the continuous ingest test.</li>
 </ul>
 </li>
-<li>Two 72-hour periods of continuous ingest with and without agitation. No validation
is necessary but the cluster should be checked to ensure it is still functional.</li>
+<li>Two 72-hour periods of continuous ingest must run. One test period must use agitation
and the other should not. No validation is necessary but the cluster should be checked to
ensure it is still functional.</li>
 </ol>
 <h2 id="releasing">Releasing</h2>
 <ol>



Mime
View raw message