Mailing-List: contact commits-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r1498207 -
 /airavata/site/trunk/content/development/release-management.mdtext
Date: Mon, 01 Jul 2013 02:45:35 -0000
To: commits@airavata.apache.org
From: smarru@apache.org
Message-Id: <20130701024535.28AD8238897A@eris.apache.org>

Author: smarru
Date: Mon Jul  1 02:45:34 2013
New Revision: 1498207

URL: http://svn.apache.org/r1498207
Log:
minor instruction update

Modified:
    airavata/site/trunk/content/development/release-management.mdtext

Modified: airavata/site/trunk/content/development/release-management.mdtext
URL: http://svn.apache.org/viewvc/airavata/site/trunk/content/development/release-management.mdtext?rev=1498207&r1=1498206&r2=1498207&view=diff
==============================================================================
--- airavata/site/trunk/content/development/release-management.mdtext (original)
+++ airavata/site/trunk/content/development/release-management.mdtext Mon Jul  1 02:45:34 2013
@@ -70,7 +70,7 @@ For reference, the steps to sign a key:
      * Ensure all open issues are resolved before proceeding further, close all resolved issues.
      * Test and make sure the release passes all regression tests.
      * Update RELEASE_NOTES with all the features added.
-     	 * The release notes can be obtained from JIRA, by clicking the version, and then configuring the release notes to display text format and copying it.
+     	 * The release notes can be obtained from JIRA, by clicking the RoadMap, version, and then configuring the release notes to display text format and copying it.
      	 * A suggested approach would be to reorganize the release notes as New Features, then Improvements then Tasks and Sub Tasks and finally Bug Fixes.
      * Review and update README, INSTALL files.
      * Commit any changes back to svn.