aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hugh...@apache.org
Subject svn commit: r796850 - in /websites/production/aries: ./ content/development/releasingaries.html
Date Mon, 10 Oct 2011 14:12:00 GMT
Author: hughesj
Date: Mon Oct 10 14:12:00 2011
New Revision: 796850

Log:
Publishing merge to aries site by hughesj

Modified:
    websites/production/aries/   (props changed)
    websites/production/aries/content/development/releasingaries.html

Propchange: websites/production/aries/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Mon Oct 10 14:12:00 2011
@@ -1 +1 @@
-/websites/staging/aries/trunk:782169-796669
+/websites/staging/aries/trunk:782169-796849

Modified: websites/production/aries/content/development/releasingaries.html
==============================================================================
--- websites/production/aries/content/development/releasingaries.html (original)
+++ websites/production/aries/content/development/releasingaries.html Mon Oct 10 14:12:00
2011
@@ -449,7 +449,7 @@ to continue to depend on the -SNAPSHOT v
 <h3 id="jira_preparation">JIRA preparation</h3>
 <ul>
 <li>After initial release discussion on the mailing list you should have a list of
JIRA issues that are required in the release. If not, the default assumption is 'everything
that has been fixed since the last release'.</li>
-<li>Make sure that there is a JIRA component that matches the name of the release,
if not, create one.</li>
+<li>Make sure that there is a JIRA version that matches the name of the release, if
not, create one.</li>
 <li>Check through defects, make sure that anything that is included in the release
has been closed. If there are open issues move them to the next release.</li>
 </ul>
 <p><a name="ReleasingAries-Creatingtherelease"></a></p>



Mime
View raw message