accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ktur...@apache.org
Subject svn commit: r1386630 - /accumulo/site/trunk/content/governance/releasing.mdtext
Date Mon, 17 Sep 2012 14:30:40 GMT
Author: kturner
Date: Mon Sep 17 14:30:39 2012
New Revision: 1386630

URL: http://svn.apache.org/viewvc?rev=1386630&view=rev
Log:
CMS commit to accumulo by kturner

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=1386630&r1=1386629&r2=1386630&view=diff
==============================================================================
--- accumulo/site/trunk/content/governance/releasing.mdtext (original)
+++ accumulo/site/trunk/content/governance/releasing.mdtext Mon Sep 17 14:30:39 2012
@@ -32,6 +32,7 @@ Note: There will be times where API comp
     - While there is currently a new trunk for the next release, it is highly discouraged
to begin committing new features to it because this is when the current release is being tested.
Any major bugs found will have to be patched in both versions and we want to make the process
as seamless as possible.
     - The new trunk needs to have its version information updated.
   - Wrap up any standing documentation endeavors, whether or not there are tickets for them.
+  - Analyze API changes since last major release and ensure there are no changes that will
cause pain for users.
   - Test the branch as per our testing criteria.
   - Once testing is deemed successful and release documentation is complete, move on to Releasing.
 
@@ -46,6 +47,7 @@ Note: There will be times where API comp
 
   1. All JUnit tests must pass.  This should be a requirement of any patch so it should never
be an issue of the codebase.
   - All functional tests must complete successfully.
+  - Analyze output of static analysis tools like Findbugs and PMD.
   - Two 24-hour periods of the randomwalk LongClean test with and without agitation need
to be run successfully on a cluster.
   - Two 24-hour periods of continuous ingest with and without agitation need to be validated
successfully on a cluster.
   - 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.
@@ -58,4 +60,4 @@ Note: There will be times where API comp
   - 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.
   - 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.
   - Upon successful vote, the new releases can be retagged to remove the RC status and released
on the Accumulo webpage.
-  - 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.
+  - 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.
\ No newline at end of file



Mime
View raw message