You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@accumulo.apache.org by bu...@apache.org on 2013/11/13 18:29:40 UTC

svn commit: r886528 - in /websites/staging/accumulo/trunk/content: ./ governance/releasing.html

Author: buildbot
Date: Wed Nov 13 17:29:39 2013
New Revision: 886528

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 Nov 13 17:29:39 2013
@@ -1 +1 @@
-1540108
+1541628

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 Nov 13 17:29:39 2013
@@ -108,6 +108,7 @@
 </li>
 <li>Wrap up any standing documentation endeavors, whether or not there are tickets for them.</li>
 <li>Analyze API changes since last major release and ensure there are no changes that will cause pain for users.</li>
+<li>Analyze and update dependencies (e.g. with mvn dependency:analyze)</li>
 <li>Test the branch as per our testing criteria.</li>
 <li>Once testing is deemed successful and release documentation is complete, move on to Releasing.</li>
 </ol>
@@ -115,6 +116,7 @@
 <ol>
 <li>Upon detection and/or resolution of a bug, discussion needs to be made on the accumulo-dev list to determine if the community thinks the bug is critical or if there have been sufficient minor bug fixes to warrant a minor release.</li>
 <li>Make any necessary documentation changes, including a change log.</li>
+<li>Analyze and update dependencies (e.g. with mvn dependency:analyze)</li>
 <li>Test the now updated branch as per our testing criteria.</li>
 <li>Once testing is deemed successful and documentation is complete, move on to Releasing.</li>
 </ol>