svn commit: r848020 - in /websites/staging/airavata/trunk/content: ./ development/release-management.html

[bu...@apache.org]

Author: buildbot
Date: Sat Jan 26 02:27:06 2013
New Revision: 848020

Log:
Staging update by buildbot for airavata

Modified:
    websites/staging/airavata/trunk/content/   (props changed)
    websites/staging/airavata/trunk/content/development/release-management.html

Propchange: websites/staging/airavata/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Jan 26 02:27:06 2013
@@ -1 +1 @@
-1438181
+1438821

Modified: websites/staging/airavata/trunk/content/development/release-management.html
==============================================================================
--- websites/staging/airavata/trunk/content/development/release-management.html (original)
+++ websites/staging/airavata/trunk/content/development/release-management.html Sat Jan 26 02:27:06 2013
@@ -121,7 +121,10 @@ The popular software used Open Pretty Go
 <ul>
 <li>Airavata requires Maven 3 or later to build and release</li>
 <li>It is encouraged to use maven's password encryption capabilities and set the gpg password in 
-~/.m2/settings.xml. Detailed instructions are at <a href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env">Publishing Maven Artifacts</a></li>
+~/.m2/settings.xml. Detailed instructions are at <a href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env">Publishing Maven Artifacts</a><ul>
+<li>Make sure both the apache.snapshots.https and apache.releases.https are configured coreectly. </li>
+</ul>
+</li>
 <li>Performing release will require maven to run series of commands, the heapsize has to be increased to avoid out of memory exceptions.</li>
 <li>Bash Shell: <code>export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m"</code>. </li>
 <li>C Shell: <code>setenv MAVEN_OPTS "-Xmx1024m -XX:MaxPermSize=256m"</code>.</li>
@@ -139,7 +142,11 @@ The popular software used Open Pretty Go
 <li>Cleanup JIRA so the Fix Version in issues resolved since the last release includes this release version correctly.</li>
 <li>Ensure all open issues are resolved before proceeding further, close all resolved issues.</li>
 <li>Test and make sure the release passes all regression tests.</li>
-<li>Update RELEASE_NOTES with all the features added. </li>
+<li>Update RELEASE_NOTES with all the features added.<ul>
+<li>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.</li>
+<li>A suggested approach would be to reorganize the release notes as New Features, then Improvements then Tasks and Sub Tasks and finally Bug Fixes.</li>
+</ul>
+</li>
 <li>Review and update README, INSTALL files.</li>
 <li>Commit any changes back to svn.</li>
 <li>Update website/wiki with Roadmap or Release landing pages.</li>
@@ -366,6 +373,10 @@ The popular software used Open Pretty Go
 <p>$ svn del https://svn.apache.org/repos/asf/airavata/tags/${project.version} -m "deleting tag from rolled back release"</p>
 </li>
 <li>
+<p>Revert the svn to old version <code>mvn -P apache-release release:rollback</code></p>
+</li>
+<li></li>
+<li>
 <p>Delete the build artifacts on people &amp; www         <br />
 </p>
 <ul>