svn commit: r1438821 - /airavata/site/trunk/content/development/release-management.mdtext

[sm...@apache.org]

Author: smarru
Date: Sat Jan 26 02:27:01 2013
New Revision: 1438821

URL: http://svn.apache.org/viewvc?rev=1438821&view=rev
Log:
updating some instructions

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=1438821&r1=1438820&r2=1438821&view=diff
==============================================================================
--- airavata/site/trunk/content/development/release-management.mdtext (original)
+++ airavata/site/trunk/content/development/release-management.mdtext Sat Jan 26 02:27:01 2013
@@ -55,6 +55,7 @@ For reference, the steps to sign a key:
 * Airavata requires Maven 3 or later to build and release
 * It is encouraged to use maven's password encryption capabilities and set the gpg password in 
 ~/.m2/settings.xml. Detailed instructions are at [Publishing Maven Artifacts][maven-artificats]
+	* Make sure both the apache.snapshots.https and apache.releases.https are configured coreectly. 
 * Performing release will require maven to run series of commands, the heapsize has to be increased to avoid out of memory exceptions.
 * 		Bash Shell: `export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m"`. 
 * 		C Shell: `setenv MAVEN_OPTS "-Xmx1024m -XX:MaxPermSize=256m"`.
@@ -68,7 +69,9 @@ For reference, the steps to sign a key:
      * Cleanup JIRA so the Fix Version in issues resolved since the last release includes this release version correctly.
      * 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. 
+     * 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.
+     	 * 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.
      * Update website/wiki with Roadmap or Release landing pages.
@@ -218,18 +221,20 @@ For reference, the steps to sign a key:
 
        $ svn del https://svn.apache.org/repos/asf/airavata/tags/${project.version} -m "deleting tag from rolled back release"
 
-4.  Delete the build artifacts on people & www           
+4. Revert the svn to old version `mvn -P apache-release release:rollback`
+5. 
+5.  Delete the build artifacts on people & www           
      *  $ rm -rfv /www/people.apache.org/builds/airavata/${project.version}
 
-4. Drop the nexus staging repo
+6. Drop the nexus staging repo
     1. https://repository.apache.org/index.html
     2. Enterprise --> Staging
     3. Staging tab --> Name column --> org.apache.airavata
     4. Right click on the closed staging repo (org.apache.airavata-XXX) and select Drop.
 
-5. Remove the staged site
+7. Remove the staged site
 
-6. Make the required updates that caused the vote to be canceled during the next release cycle
+8. Make the required updates that caused the vote to be canceled during the next release cycle
 
 <a name="verify_signatures"></a>
 ####Verifying release signatures