accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r894219 - in /websites/staging/accumulo/trunk/content: ./ governance/releasing.html
Date Wed, 15 Jan 2014 05:29:26 GMT
Author: buildbot
Date: Wed Jan 15 05:29:26 2014
New Revision: 894219

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 Wed Jan 15 05:29:26 2014
@@ -1 +1 @@
-1558294
+1558295

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 Wed Jan 15 05:29:26
2014
@@ -121,13 +121,39 @@
 <li>Once testing is deemed successful and documentation is complete, move on to Releasing.</li>
 </ol>
 <h2 id="testing">Testing</h2>
+<p>Testing for an Accumulo release includes a few steps that a developer may take without
a Hadoop cluster and several that require a working cluster.</p>
+<h3 id="stand-alone">Stand alone</h3>
+<p>The following steps can be taken without having an underlying cluster. They SHOULD
be handled with each Hadoop profile available for a given release version. To activate an
alternative profile specify e.g. "-Dhadoop.profile=2" for the Hadoop 2 profile on the Maven
commandline. Some older versions of Accumulo referred to Hadoop profiles diferently; see the
README that came with said versions for details on building against different Hadoop versions.</p>
 <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>All JUnit tests must pass.  This should be a requirement of any patch so it should
never be an issue of the codebase.<ul>
+<li>Use "mvn package" to run against the default profile of a particular release</li>
+<li>Use "mvn -Dhadoop.profile=2 package" to test against the Hadoop 2 profile on e.g.
1.4 or 1.5</li>
+<li>Use "mvn -Dhadoop.profile=1 package" to test against the Hadoop 1 profile on e.g.
1.6 or later</li>
+</ul>
+</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>
+<li>For versions 1.6 and later, all functional tests must pass via the Maven failsafe
plugin.<ul>
+<li>Use "mvn verify" to run against the default profile of a particular release</li>
+<li>Use "mvn -Dhadoop.profile=1 verify" to run the functional tests against the Hadoop
1 profile</li>
+</ul>
+</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>
+<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>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>
+</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>
 </ol>
 <h2 id="releasing">Releasing</h2>
 <ol>
@@ -137,7 +163,10 @@
 </ul>
 </li>
 <li>PGP Signatures of the tarball must be signed to a separate file and made available
in the public_html folder of the user creating the release on people.apache.org, along with
the tarball and MD5 and SHA512 checksums.</li>
-<li>A vote must be made on dev@accumulo. Lazy consensus is not sufficient for a release;
at least 3 +1 votes from PMC members are required. All checksums and signatures need to be
verified before any voter can +1 it. Voting shall last 72 hours.</li>
+<li>A vote must be made on dev@accumulo. Lazy consensus is not sufficient for a release;
at least 3 +1 votes from PMC members are required. All checksums and signatures need to be
verified before any voter can +1 it. Voting shall last 72 hours.<ul>
+<li>Voters SHOULD include with their vote details on the tests from the testing section
they have successfully run. If given, said details for each test MUST include: the number
of worker nodes in the cluster, the operating system and version, the Hadoop version, and
the Zookeeper version. All such gathered testing information will be included in the release
notes. </li>
+</ul>
+</li>
 <li>Upon successful vote, the new releases can be retagged to remove the RC status
and released on the Accumulo webpage.</li>
 <li>If at any time the tag needs to be remade due to any sort of error, it should be
incremented to the next release candidate number.</li>
 </ol>



Mime
View raw message