svn commit: r1073073 - /aries/site/trunk/content/development/releasingaries.mdtext

[zo...@apache.org]

Author: zoe
Date: Mon Feb 21 17:16:16 2011
New Revision: 1073073

URL: http://svn.apache.org/viewvc?rev=1073073&view=rev
Log:
adding instructions for JIRA

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=1073073&r1=1073072&r2=1073073&view=diff
==============================================================================
--- aries/site/trunk/content/development/releasingaries.mdtext (original)
+++ aries/site/trunk/content/development/releasingaries.mdtext Mon Feb 21 17:16:16 2011
@@ -27,6 +27,7 @@ There are a few steps to the process:
  1. Creating and storing GPG keys
  1. Setting up your environment
  1. Creating a branch to release from
+ 1. JIRA preparation
  1. Checking release artifacts on your local system
  1. Creating a snapshot release (optional - not really part of the release
 process, uses mvn deploy)
@@ -36,6 +37,7 @@ release:perform)
  1. Promoting the release artifacts to the Apache release repository
  1. Making the release artifacts available from the Aries web pages
  1. What to do when people find problems with the release artifacts
+ 1. JIRA tasks
 
 The best current documentation for releases is [here](http://apache.org/dev/publishing-maven-artifacts.html)
  - but this isn't released yet. It covers all the steps listed above so on
@@ -144,6 +146,12 @@ file does need one. As an alternative yo
 TBD. This isn't a necessary step in the release process but should still be
 documented here.
 
+### 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.
+  * 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.
+
+
 <a name="ReleasingAries-Creatingtherelease"></a>
 ### Creating the release
 
@@ -329,7 +337,7 @@ Download the release artifacts using a s
    or use a fancy editor.
   * Get the compliance tests run
   * Release notes
-  * Tidy up JIRA
+  * Release the component in JIRA (manage components), check the JIRA release notes.
 
 
 <a name="ReleasingAries-Whattodowhenpeoplefindproblemswiththerelease"></a>