You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@aries.apache.org by bu...@apache.org on 2011/10/10 16:11:48 UTC
svn commit: r796849 -
/websites/staging/aries/trunk/content/development/releasingaries.html
Author: buildbot
Date: Mon Oct 10 14:11:48 2011
New Revision: 796849
Log:
Staging update by buildbot
Modified:
websites/staging/aries/trunk/content/development/releasingaries.html
Modified: websites/staging/aries/trunk/content/development/releasingaries.html
==============================================================================
--- websites/staging/aries/trunk/content/development/releasingaries.html (original)
+++ websites/staging/aries/trunk/content/development/releasingaries.html Mon Oct 10 14:11:48 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>