accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r899346 - in /websites/staging/accumulo/trunk/content: ./ releasing.html
Date Thu, 27 Feb 2014 02:45:27 GMT
Author: buildbot
Date: Thu Feb 27 02:45:27 2014
New Revision: 899346

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 Thu Feb 27 02:45:27 2014
@@ -1 +1 @@

Modified: websites/staging/accumulo/trunk/content/releasing.html
--- websites/staging/accumulo/trunk/content/releasing.html (original)
+++ websites/staging/accumulo/trunk/content/releasing.html Thu Feb 27 02:45:27 2014
@@ -105,6 +105,14 @@
 <li>Have a clean workspace before starting.</li>
 <p>Given all of this, it's recommended that you only attempt making a release from
a GNU/Linux machine.</p>
+<h3 id="update-changes">Update CHANGES</h3>
+<p>The CHANGES file should, at a minimum, contain all Jira completed issues from the
current "major" release line 
+(e.g. for 1.5.2, CHANGES would contain 1.5.2, 1.5.1 and 1.5.0 Jira issues). Issues that did
+result in an actual change (e.g. "Duplicate", "Invalid", "Won't Fix" resolutions) should
not be included
+in the file. The changes should be ordered by version number in descending order, grouped
by Jira 
+issue type. There is still disagreement if issues from all previous versions that are contained
+the present version should be listed (including issues from former major releases); as of
+it was agreed upon to omit issues from previous major versions.</p>
 <h2 id="create-the-candidate">Create the candidate</h2>
 <p>You should use the provided script assemble/ to create the release candidate.
This script is
 desirable as it activates all necessary maven profiles in addition to verifying that certain

View raw message