You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@aries.apache.org by hu...@apache.org on 2011/10/10 16:11:41 UTC
svn commit: r1180983 -
/aries/site/trunk/content/development/releasingaries.mdtext
Author: hughesj
Date: Mon Oct 10 14:11:40 2011
New Revision: 1180983
URL: http://svn.apache.org/viewvc?rev=1180983&view=rev
Log:
It's a 'JIRA version' that's needed at release time not a component
Modified:
aries/site/trunk/content/development/releasingaries.mdtext
Modified: aries/site/trunk/content/development/releasingaries.mdtext
URL: http://svn.apache.org/viewvc/aries/site/trunk/content/development/releasingaries.mdtext?rev=1180983&r1=1180982&r2=1180983&view=diff
==============================================================================
--- aries/site/trunk/content/development/releasingaries.mdtext (original)
+++ aries/site/trunk/content/development/releasingaries.mdtext Mon Oct 10 14:11:40 2011
@@ -248,7 +248,7 @@ to continue to depend on the -SNAPSHOT v
### JIRA preparation
* 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'.
- * Make sure that there is a JIRA component that matches the name of the release, if not, create one.
+ * Make sure that there is a JIRA version that matches the name of the release, if not, create one.
* 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.