rave-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mfrank...@apache.org
Subject svn commit: r1137702 - in /incubator/rave/site/trunk/content/rave: release-process.mdtext release-setup.mdtext
Date Mon, 20 Jun 2011 17:01:00 GMT
Author: mfranklin
Date: Mon Jun 20 17:00:59 2011
New Revision: 1137702

URL: http://svn.apache.org/viewvc?rev=1137702&view=rev
Log:
Updated release process.

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

Modified: incubator/rave/site/trunk/content/rave/release-process.mdtext
URL: http://svn.apache.org/viewvc/incubator/rave/site/trunk/content/rave/release-process.mdtext?rev=1137702&r1=1137701&r2=1137702&view=diff
==============================================================================
--- incubator/rave/site/trunk/content/rave/release-process.mdtext (original)
+++ incubator/rave/site/trunk/content/rave/release-process.mdtext Mon Jun 20 17:00:59 2011
@@ -16,15 +16,23 @@ Notice:    Licensed to the Apache Softwa
            specific language governing permissions and limitations
            under the License.
 
-###Incubator Release Steps
+###Incubator Release Steps Overview
+There are two distinct sets of artifacts that are released on independent schedules:  rave-master
& rave-project.  The rave-master is the project metadata (committers, roles, etc) and
only needs to be released when there is a change in the structure of the project itself (committers,
mentors, etc).  The rave-project artifacts are comprised of all rave source code, binaries
and a standalone demo.  
 
-1. Environment setup for releasing artifacts (same for SNAPSHOTs and releases) -
-  1. Increase the default Java heap available to Maven (required for Java SE 6)  
+The following steps are performed for each of the rave-project and rave-master releases separately.
 
-        export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m"
-  2. Use the latest Sun 1.6.0 JDK
-  3. Use Maven 3.0.3 or later
-  4. Make sure the [Release Setup](release-setup.html) steps have been performed.
+####Common Release Steps
+
+1. Environment setup for releasing artifacts (same for SNAPSHOTs and releases)    
+   
+    1. Increase the default Java heap available to Maven (required for Java SE 6)   
+
+          export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m" 
+
+    2. Use the latest Sun 1.6.0 JDK
+    3. Use Maven 3.0.3 or later
+
+    4. Make sure the [Release Setup](release-setup.html) steps have been performed.
 
 2. Prepare the source for release:     
      1. Cleanup JIRA so the Fix Version in issues resolved since the last release includes
this release version correctly. Also, transition any Resolved issues to the Closed state.
@@ -36,38 +44,40 @@ Notice:    Licensed to the Apache Softwa
 
 3. Checkout a clean copy of the trunk to release using command line svn.   
 
-   *Do not use Eclipse to do the checkout. The extra dot (.) files created by Eclipse throws
off the rat:check processing.*
+    *Do not use Eclipse to do the checkout. The extra dot (.) files created by Eclipse throws
off the rat:check processing.*
 
 4. Use `mvn -P pedantic verify` to verify the source has the required headers before trying
to release.
 
 5. Do a dry run of the release:prepare step:  
        
-        $ mvn -Papache-release release:prepare -DdryRun=true
+        $ mvn -P apache-release release:prepare -DdryRun=true
 
-   The dry run will not commit any changes back to SVN and gives you the opportunity to verify
that the release process will complete as expected. You will be prompted for the following
information :
+    The dry run will not commit any changes back to SVN and gives you the opportunity to
verify that the release process will complete as expected. You will be prompted for the following
information :  
+      
       * Release version - take the default 
       * SCM release tag - *DO NOT TAKE THE DEFAULT*  -: : 0.1-incubating
       * New development version - take the default
       * GPG Passprhase  
 
-  *If you cancel a release:prepare before it updates the pom.xml versions, then use the release:clean
goal to just remove the extra files that were created.*
+    *If you cancel a release:prepare before it updates the pom.xml versions, then use the
release:clean goal to just remove the extra files that were created.*  
 
 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 -   
 
-            $ svn commit -m "fixing formatting for release"
+            $ svn commit -m "fixing formatting for release"  
+
     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](http://incubator.apache.org/rave/release-process.html#verify_signatures))
+    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 -Papache-release release:rollback
+        $ mvn -P apache-release release:rollback
 
 8. Prepare the release
    1. Run the "release:prepare" step for real this time. You'll be prompted for the same
version information.
 	
-          $ mvn release:prepare -Papache-release -DpreparationGoals="clean install cargo:package"
+          $ mvn -P dist release:prepare
 
    2. Backup (zip or tar) your local release candidate directory in case you need to rollback
the release after the next step is performed.
 
@@ -124,7 +134,7 @@ Notice:    Licensed to the Apache Softwa
        3. Staging tab --> Name column --> org.apache.rave
        4. Right click on the closed staging repo (org.apache.rave-XXX) and select Promote.
 
-    2. Copy the distribution artifacts over to the distribution area
+    2. Copy the distribution artifacts over to the distribution area (for rave-project only)
 
           $ ssh ${user.name}@people.apache.org  
           $ mkdir /www/www.apache.org/dist/incubator/rave/${project.version}   
@@ -178,7 +188,7 @@ Notice:    Licensed to the Apache Softwa
 6. Make the required updates that caused the vote to be canceled
 7. Spin another release candidate!
 
-
+<a name="verify_signatures" />
 ####Verifying release signatures
 On unix platforms the following command can be executed -
 

Modified: incubator/rave/site/trunk/content/rave/release-setup.mdtext
URL: http://svn.apache.org/viewvc/incubator/rave/site/trunk/content/rave/release-setup.mdtext?rev=1137702&r1=1137701&r2=1137702&view=diff
==============================================================================
--- incubator/rave/site/trunk/content/rave/release-setup.mdtext (original)
+++ incubator/rave/site/trunk/content/rave/release-setup.mdtext Mon Jun 20 17:00:59 2011
@@ -89,3 +89,6 @@ These setup steps only need to be perfor
 
 6. Following the instructions in http://people.apache.org/~henkp/trust/ and ask multiple
(at least 3) current Apache committers to sign your public key.
 
+####Configure Maven
+
+1. Update your ~/.m2/settings.xml with the properties from [Publishing Maven Artifacts](http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env)



Mime
View raw message