rave-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mfrank...@apache.org
Subject svn commit: r1138184 - /incubator/rave/site/trunk/content/rave/release-process.mdtext
Date Tue, 21 Jun 2011 21:04:50 GMT
Author: mfranklin
Date: Tue Jun 21 21:04:50 2011
New Revision: 1138184

URL: http://svn.apache.org/viewvc?rev=1138184&view=rev
Log:
Updated with steps for releasing demo binaries

Modified:
    incubator/rave/site/trunk/content/rave/release-process.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=1138184&r1=1138183&r2=1138184&view=diff
==============================================================================
--- incubator/rave/site/trunk/content/rave/release-process.mdtext (original)
+++ incubator/rave/site/trunk/content/rave/release-process.mdtext Tue Jun 21 21:04:50 2011
@@ -55,7 +55,7 @@ The following steps are performed for ea
     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
+      * SCM release tag - *DO NOT TAKE THE DEFAULT*  -: : ${project.version}-incubating
       * New development version - take the default
       * GPG Passprhase  
 
@@ -75,83 +75,94 @@ The following steps are performed for ea
         $ 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.
+
+    1. Run the "release:prepare" step for real this time. You'll be prompted for the same
version information.
 	
-          $ mvn -P dist release:prepare
+          $ mvn -P apache-release 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.
+    2. Backup (zip or tar) your local release candidate directory in case you need to rollback
the release after the next step is performed.
 
 9. Perform the release
-
-  This step will create a maven staging repository and site for use in testing and voting.

+     * This step will create a maven staging repository and site for use in testing and voting.

 
         $ mvn release:perform -Papache-release -Duser.name=<your_apache_uid>
    
-    *If your local OS userid doesn't match your Apache userid, then you'll have to also override
the value provided by the OS to Maven for the site-deploy step to work. This is known to work
for Linux, but not for Mac and unknown for Windows.*
-    *The maven-release-plugin is configured with goals "deploy site site:deploy" and will
deploy the site files to a staging-site directory on people.apache.org.*
+     * *If your local OS userid doesn't match your Apache userid, then you'll have to also
override the value provided by the OS to Maven for the site-deploy step to work. This is known
to work for Linux, but not for Mac and unknown for Windows.*
+
 10. Verify the release artifacts
-   1. Verify the HTML links in site are correct
-   2. Verify the staged artifacts in the nexus repo          
-           1. https://repository.apache.org/index.html
-           2. Enterprise --> Staging
-           3. Staging tab --> Name column --> org.apache.rave
-           4. 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
-     1. https://repository.apache.org/index.html
-     2. Enterprise --> Staging
-     3. Staging tab --> Name column --> org.apache.rave
-     4. Right click on the open staging repo (org.apache.rave-XXX) and select Close.
+    
+    1. Verify the HTML links in site are correct
+    
+    2. Verify the staged artifacts in the nexus repo     
+        * https://repository.apache.org/index.html
+        * Enterprise --> Staging
+        * Staging tab --> 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
+        * https://repository.apache.org/index.html
+        * Enterprise --> Staging
+        * Staging tab --> Name column --> org.apache.rave
+        * Right click on the open staging repo (org.apache.rave-XXX) and select Close.
+
 11. Put the release candidate up for a vote
      1. Create a VOTE email thread on rave-dev@ to record votes as replies, like [this](release-vote.txt)
      2. Create a DISCUSS email thread on rave-dev@ for any vote questions, [this](release-discuss.txt)
      3. Perform a review of the release and cast your vote. See the following for more details
on Apache releases 
 
-     [http://www.apache.org/dev/release.html](http://www.apache.org/dev/release.html)  
-     [http://incubator.apache.org/guides/releasemanagement.html](http://incubator.apache.org/guides/releasemanagement.html)
+           [http://www.apache.org/dev/release.html](http://www.apache.org/dev/release.html)
 
+           [http://incubator.apache.org/guides/releasemanagement.html](http://incubator.apache.org/guides/releasemanagement.html)
 
      4. A -1 vote does not necessarily mean that the vote must be redone, however it is usually
a good idea to rollback the release if a -1 vote is received. See - Recovering from a vetoed
release
      5. After the vote has been open for at least 72 hours, has at least three +1 PMC votes
and no -1 votes, then post the results to the vote thread by -
-         1. reply to the initial email and prepend to the original subject -
-
-         [RESULTS]
-
-         2. Include a list of everyone who voted +1, 0 or -1.
+         * reply to the initial email and prepend to the original subject "[RESULTS]"
+         * Include a list of everyone who voted +1, 0 or -1.
 
 12. Put the release candidate up for an Incubator PMC vote
     1. Create a VOTE email thread on general@incubator to record votes as replies, like [this](vote-ipmc.txt)
 
     2. After the vote has been open for at least 72 hours, has at least three +1 Incubator
PMC votes and no -1 votes, then post the results to the vote thread by -
-        1. replying to the initial email and prepend to the original subject -
-
-         [RESULTS]
-
-        2. Include a list of everyone who voted +1, 0 or -1.
+        * replying to the initial email and prepend to the original subject  "[RESULTS]"
+        * Include a list of everyone who voted +1, 0 or -1.
 
 13. Finalizing a release
-   1. Promote the staged nexus artifacts -
-       1. https://repository.apache.org/index.html
-       2. Enterprise --> Staging
-       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 (for rave-project only)
-
-          $ ssh ${user.name}@people.apache.org  
-          $ mkdir /www/www.apache.org/dist/incubator/rave/${project.version}   
-          $ cd /www/www.apache.org/dist/incubator/rave/${project.version}   
-          $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip
   
-          $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip.asc
  
-          $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip.md5
  
-          $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip.sha1
   
 
-     **Make sure all the copied files have g+rw set and only o+r set**
+    1. Promote the staged nexus artifacts  
 
-          $ find . -user ${user.name} -type f | xargs chmod 664
-          $ find . -user ${user.name} -type d | xargs chmod 775
+        * https://repository.apache.org/index.html
+        * Enterprise --> Staging
+        * Staging tab --> Name column --> org.apache.rave
+        * Right click on the closed staging repo (org.apache.rave-XXX) and select Promote.
+
+    2. Build and sign the standalone demo (for rave-project releases only):  
+
+        * Checkout the tag from SVN 
+        * $ mvn -P dist
+        * $ gpg -ab ./rave-portal/target/rave-*${project.version}*-incubating.bin.zip
+        * $ gpg -ab ./rave-portal/target/rave-*${project.version}*-incubating.bin.tar.gz
+        * $ gpg --print-md SHA512 rave-*${project.version}*-incubating.bin.zip > rave-*${project.version}*-incubating.bin.zip.sha
+        * $ gpg --print-md SHA512 rave-*${project.version}*-incubating.bin.tar.gz > rave-*${project.version}*-incubating.bin.zip.sha
+        * $ gpg --print-md MD5 rave-*${project.version}*-incubating.bin.zip > rave-*${project.version}*-incubating.bin.zip.md5
+        * $ gpg --print-md MD5 rave-*${project.version}*-incubating.bin.tar.gz > rave-*${project.version}*-incubating.bin.zip.md5
+
+    3. 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}   
+        *  $ cd /www/www.apache.org/dist/incubator/rave/${project.version}   
+        *  $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-project/${project.version}/rave-parent-${project.version}-source-release.zip
   
+        *  $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-project/${project.version}/rave-parent-${project.version}-source-release.zip.asc
  
+        *  $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-project/${project.version}/rave-parent-${project.version}-source-release.zip.md5
  
+        *  $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-project/${project.version}/rave-parent-${project.version}-source-release.zip.sha1
   
+        *  Make sure all the copied files have g+rw set and only o+r set
+
+               $ find . -user ${user.name} -type f | xargs chmod 664  
+               $ find . -user ${user.name} -type d | xargs chmod 775
+     
+        *  $ exit
+        *  $ scp ./rave-portal/target/rave-*${project.version}*-incubating.bin.* ${user.name}@people.apache.org:/www/www.apache.org/dist/incubator/rave/${project.version}/
 
-     *Note: All of the artifacts are in the maven repos, but we may create an assembly to
publish in future releases*
-    
-    3. Publish the staged website 
+    4. Publish the staged website   
 
 14. Update the JIRA versions page to mark the version as "released", and set the date to
the date that the release was approved. You may also need to make a new release entry for
the next release.
 15. Announcing the release



Mime
View raw message