accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r982119 - in /websites/staging/accumulo/trunk/content: ./ governance/releasing.html
Date Mon, 07 Mar 2016 20:07:18 GMT
Author: buildbot
Date: Mon Mar  7 20:07:18 2016
New Revision: 982119

Staging update by buildbot for accumulo

    websites/staging/accumulo/trunk/content/   (props changed)

Propchange: websites/staging/accumulo/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Mon Mar  7 20:07:18 2016
@@ -1 +1 @@

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 Mar  7 20:07:18
@@ -272,7 +272,7 @@ release, the release should be vetoed vi
 <li>Be fully built, including a tar.gz of the entire project as well as the documentation.</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, along with
the tarball and MD5 and SHA512 checksums.</li>
+<li>PGP Signatures of the tarball must be signed to a separate file and made available
to the public, along with the tarball and MD5 and SHA512 checksums. The <a href="">Apache
Nexus server</a> fills this role for us via the maven-release-plugin.</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.  For testing done on a version other than the release candidate that
is deemed relevant, include the commit hash. All such gathered testing information will be
included in the release notes. </li>

View raw message