accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bus...@apache.org
Subject svn commit: r1581267 - /accumulo/site/trunk/content/governance/releasing.mdtext
Date Tue, 25 Mar 2014 07:29:05 GMT
Author: busbey
Date: Tue Mar 25 07:29:05 2014
New Revision: 1581267

URL: http://svn.apache.org/r1581267
Log:
per dev-list DISCUSS thread, clarifying language around release tests.

Modified:
    accumulo/site/trunk/content/governance/releasing.mdtext

Modified: accumulo/site/trunk/content/governance/releasing.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/trunk/content/governance/releasing.mdtext?rev=1581267&r1=1581266&r2=1581267&view=diff
==============================================================================
--- accumulo/site/trunk/content/governance/releasing.mdtext (original)
+++ accumulo/site/trunk/content/governance/releasing.mdtext Tue Mar 25 07:29:05 2014
@@ -62,15 +62,15 @@ The following steps can be taken without
     - Use "mvn -Dhadoop.profile=1 verify" to run the functional tests against the Hadoop
1 profile
 
 ### Cluster based
-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.
+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.
 
   1. For versions prior to 1.6, all functional tests must complete successfully.
     - See $ACCUMULO_HOME/test/system/auto/README for details on running the functional tests.
-  - Two 24-hour periods of the randomwalk LongClean test with and without agitation need
to be run successfully.
+  - 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.
     - See $ACCUMULO_HOME/test/system/randomwalk/README for details on running the LongClean
module.
-  - Two 24-hour periods of continuous ingest with and without agitation need to be validated
successfully.
-    - See $ACCUMULO_HOME/test/system/continuous/README for details on running and verifying
the continous ingest test.
-  - 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.
+  - Two 24-hour periods of the continuous ingest test must be validated successfully. One
test period must use agitation and the other should not.
+    - See $ACCUMULO_HOME/test/system/continuous/README for details on running and verifying
the continuous ingest test.
+  - 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.
 
 ## Releasing
 



Mime
View raw message