svn commit: r1355602 - /rave/site/trunk/content/release-process.mdtext

[at...@apache.org]

Author: ate
Date: Fri Jun 29 23:31:29 2012
New Revision: 1355602

URL: http://svn.apache.org/viewvc?rev=1355602&view=rev
Log:
CMS commit to rave by ate

Modified:
    rave/site/trunk/content/release-process.mdtext

Modified: rave/site/trunk/content/release-process.mdtext
URL: http://svn.apache.org/viewvc/rave/site/trunk/content/release-process.mdtext?rev=1355602&r1=1355601&r2=1355602&view=diff
==============================================================================
--- rave/site/trunk/content/release-process.mdtext (original)
+++ rave/site/trunk/content/release-process.mdtext Fri Jun 29 23:31:29 2012
@@ -67,16 +67,12 @@ All of the steps below apply to both the
 
 6. Verify that the release process completed as expected
     1. The release plugin will create pom.xml.tag files which contain the changes that would have been committed to SVN. The only differences between pom.xml.tag and it's corresponding pom.xml file should be the version number.
-    2. If other formatting changes have been made you should review the changes and then commit them -   
+    2. Check release.properties and make sure that the scm properties have the right version. Sometimes the scm location can be the previous version not the next version.
+    3. Verify signatures ([Verifying release signatures](#verify_signatures))
 
-            $ svn commit -m "fixing formatting for release"  
+7. Cleanup the release prepare files again:  
 
-    3. Check release.properties and make sure that the scm properties have the right version. Sometimes the scm location can be the previous version not the next version.
-    4. Verify signatures ([Verifying release signatures](#verify_signatures))
-
-7. Once any failures or required updates have been committed to svn, rollback the release prepare files:  
-
-        $ mvn -P apache-release release:rollback
+        $ mvn -P apache-release release:clean
 
 8. Prepare the release
 
@@ -97,14 +93,12 @@ All of the steps below apply to both the
 
 10. Verify the Nexus release artifacts
     
-    1. Verify the HTML links in site are correct
-    
-    2. Verify the staged artifacts in the nexus repo     
+    1. Verify the staged artifacts in the nexus repo     
         * https://repository.apache.org/index.html
         * Staging repositories (under Build Promotion) --> Name column --> org.apache.rave
         * Navigate through the artifact tree and make sure that all javadoc, sources, tests, jars, ... have .asc (GPG signature) and .md5 files. See http://people.apache.org/~henkp/repo/faq.html and http://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig
     
-    3. Close the nexus staging repo
+    2. Close the nexus staging repo
         * https://repository.apache.org/index.html
         * Staging repositories (under Build Promotion) --> Name column --> org.apache.rave
         * Click checkbox for the open staging repo (org.apache.rave-XXX) and press Close in the menu bar.
@@ -115,17 +109,17 @@ All of the steps below apply to both the
 
         * Checkout the tag from SVN 
         * $ mvn -P dist
-        * $ gpg -ab ./rave-portal/target/rave-*${project.version}*.bin.zip
-        * $ gpg -ab ./rave-portal/target/rave-*${project.version}*.bin.tar.gz
-        * $ gpg --print-md SHA512 rave-*${project.version}*.bin.zip > rave-*${project.version}*.bin.zip.sha
-        * $ gpg --print-md SHA512 rave-*${project.version}*.bin.tar.gz > rave-*${project.version}*.bin.zip.sha
-        * $ gpg --print-md MD5 rave-*${project.version}*.bin.zip > rave-*${project.version}*.bin.zip.md5
-        * $ gpg --print-md MD5 rave-*${project.version}*.bin.tar.gz > rave-*${project.version}*.bin.zip.md5
+        * $ gpg -ab ./rave-portal/target/apache-rave-*${project.version}*.bin.zip
+        * $ gpg -ab ./rave-portal/target/apache-rave-*${project.version}*.bin.tar.gz
+        * $ gpg --print-md SHA512 apache-rave-*${project.version}*.bin.zip > apache-rave-*${project.version}*.bin.zip.sha
+        * $ gpg --print-md SHA512 apache-rave-*${project.version}*.bin.tar.gz > apache-rave-*${project.version}*.bin.tar.gz.sha
+        * $ gpg --print-md MD5 apache-rave-*${project.version}*.bin.zip > apache-rave-*${project.version}*.bin.zip.md5
+        * $ gpg --print-md MD5 apache-rave-*${project.version}*.bin.tar.gz > apache-rave-*${project.version}*.bin.tar.gz.md5
 
      2. Copy the artifacts to the staging area
         
         * $ ssh people.apache.org mkdir /www/people.apache.org/builds/rave/${project.version}
-        * $ scp ./rave-portal/target/rave-*${project.version}*.bin.* ${user.name}@people.apache.org:/www/people.apache.org/builds/rave/${project.version}/
+        * $ scp ./rave-portal/target/apache-rave-*${project.version}*.bin.* ${user.name}@people.apache.org:/www/people.apache.org/builds/rave/${project.version}/
         * Verify they are downloadable from http://people.apache.org/builds/rave/${project.version}/
 
 11. Put the release candidate up for a vote