accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From els...@apache.org
Subject svn commit: r1572413 - /accumulo/site/trunk/content/releasing.mdtext
Date Thu, 27 Feb 2014 02:45:14 GMT
Author: elserj
Date: Thu Feb 27 02:45:14 2014
New Revision: 1572413

URL: http://svn.apache.org/r1572413
Log:
ACCUMULO-2394 Write down what should be in CHANGES

Modified:
    accumulo/site/trunk/content/releasing.mdtext

Modified: accumulo/site/trunk/content/releasing.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/trunk/content/releasing.mdtext?rev=1572413&r1=1572412&r2=1572413&view=diff
==============================================================================
--- accumulo/site/trunk/content/releasing.mdtext (original)
+++ accumulo/site/trunk/content/releasing.mdtext Thu Feb 27 02:45:14 2014
@@ -33,6 +33,16 @@ There are number of things that are requ
 
 Given all of this, it's recommended that you only attempt making a release from a GNU/Linux
machine.
 
+### Update CHANGES
+
+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
not 
+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
in
+the present version should be listed (including issues from former major releases); as of
1.5.1,
+it was agreed upon to omit issues from previous major versions.
+
 ## Create the candidate
 
 You should use the provided script assemble/build.sh to create the release candidate. This
script is



Mime
View raw message