You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@continuum.apache.org by br...@apache.org on 2010/04/29 03:47:42 UTC

svn commit: r939167 - /continuum/site/src/site/apt/development/release.apt

Author: brett
Date: Thu Apr 29 01:47:41 2010
New Revision: 939167

URL: http://svn.apache.org/viewvc?rev=939167&view=rev
Log:
update release notes

Modified:
    continuum/site/src/site/apt/development/release.apt

Modified: continuum/site/src/site/apt/development/release.apt
URL: http://svn.apache.org/viewvc/continuum/site/src/site/apt/development/release.apt?rev=939167&r1=939166&r2=939167&view=diff
==============================================================================
--- continuum/site/src/site/apt/development/release.apt (original)
+++ continuum/site/src/site/apt/development/release.apt Thu Apr 29 01:47:41 2010
@@ -44,8 +44,6 @@ Continuum Release Preparation
 
   []
 
- [[1]] Update the <<<site.xml>>> for version changes
-
  [[1]] Make sure that you have the "release" profile set in your <<<settings.xml>>> as shown below.
 
 +-----+
@@ -62,82 +60,31 @@ Continuum Release Preparation
 Continuum Release Process
 
  By default, the release will be staged in <<<http://people.apache.org/builds/continuum/$\{version\}/staging-repo>>>.
- If you want to stage it elsewhere, set the <<<deploy.altRepository>>> property in your <<<settings.xml>>> file.
-
- [[1]] Execute <<<mvn release:prepare>>> (check that it has been properly tagged. The tag name must be <<<continuum-[VERSION]>>>)
+ If you want to stage it elsewhere, set the <<<deploy.altRepository>>> property in your <<<settings.xml>>> file. For example:
 
- <<Note:>> SCM tag does not work with Subversion \> 1.5.1
+----
+<deploy.altRepository>vmbuild.staging::default::http://vmbuild.apache.org/archiva/repository/staged-continuum/</deploy.altRepository>
+----
 
-  * Use subversion 1.4.1 or
+  <Note:> If using Archiva to deploy to, you will need to clear the deployment repository first
 
-  * After SCM tag fails with an error 'svn: File ... already exists',
-    do an svn update first then resume the release preparation from the SCM tag phase.
+ [[1]] Check trunk is building correctly (including Selenium tests) by running:
 
-+-----+
-svn up
-mvn release:prepare
-+-----+
+----
+mvn clean install -Pintegration
+----
 
-  []
+ [[1]] Execute <<<mvn release:prepare>>> (check that it has been properly tagged. The tag name must be <<<continuum-[VERSION]>>>)
 
  [[1]] Then execute <<<mvn release:perform>>>
 
  [[1]] ssh to <<<people.apache.org>>> and cd to <<</www/people.apache.org/builds/continuum/VERSION>>>.  Execute the following commands to copy and rename the source and binary distributions.
 
 +-----+
-export VER=1.3.4
-
-find staging-repo -name "*.zip*"    -exec cp {} . \;
-find staging-repo -name "*.tar.gz*" -exec cp {} . \;
-find staging-repo -name "*.war*"    -exec cp {} . \;
-find . -name "*.asc.*" -exec rm {} \;
-
-mv continuum-$VER.zip apache-continuum-$VER-src.zip
-mv continuum-$VER.zip.md5 apache-continuum-$VER-src.zip.md5
-mv continuum-$VER.zip.sha1 apache-continuum-$VER-src.zip.sha1
-mv continuum-$VER.zip.asc apache-continuum-$VER-src.zip.asc
-
-mv continuum-jetty-$VER-bin.tar.gz apache-continuum-$VER-bin.tar.gz
-mv continuum-jetty-$VER-bin.tar.gz.md5 apache-continuum-$VER-bin.tar.gz.md5
-mv continuum-jetty-$VER-bin.tar.gz.sha1 apache-continuum-$VER-bin.tar.gz.sha1
-mv continuum-jetty-$VER-bin.tar.gz.asc apache-continuum-$VER-bin.tar.gz.asc
-
-mv continuum-jetty-$VER-bin.zip apache-continuum-$VER-bin.zip
-mv continuum-jetty-$VER-bin.zip.md5 apache-continuum-$VER-bin.zip.md5
-mv continuum-jetty-$VER-bin.zip.sha1 apache-continuum-$VER-bin.zip.sha1
-mv continuum-jetty-$VER-bin.zip.asc apache-continuum-$VER-bin.zip.asc
-
-mv continuum-webapp-$VER.war apache-continuum-$VER.war
-mv continuum-webapp-$VER.war.asc apache-continuum-$VER.war.asc
-mv continuum-webapp-$VER.war.md5 apache-continuum-$VER.war.md5
-mv continuum-webapp-$VER.war.sha1 apache-continuum-$VER.war.sha1
-
-mv continuum-buildagent-jetty-$VER-bin.tar.gz apache-continuum-buildagent-$VER-bin.tar.gz
-mv continuum-buildagent-jetty-$VER-bin.tar.gz.md5 apache-continuum-buildagent-$VER-bin.tar.gz.md5
-mv continuum-buildagent-jetty-$VER-bin.tar.gz.sha1 apache-continuum-buildagent-$VER-bin.tar.gz.sha1
-mv continuum-buildagent-jetty-$VER-bin.tar.gz.asc apache-continuum-buildagent-$VER-bin.tar.gz.asc
-
-mv continuum-buildagent-jetty-$VER-bin.zip apache-continuum-buildagent-$VER-bin.zip
-mv continuum-buildagent-jetty-$VER-bin.zip.md5 apache-continuum-buildagent-$VER-bin.zip.md5
-mv continuum-buildagent-jetty-$VER-bin.zip.sha1 apache-continuum-buildagent-$VER-bin.zip.sha1
-mv continuum-buildagent-jetty-$VER-bin.zip.asc apache-continuum-buildagent-$VER-bin.zip.asc
-
-mv continuum-buildagent-webapp-$VER.war apache-continuum-buildagent-$VER.war
-mv continuum-buildagent-webapp-$VER.war.asc apache-continuum-buildagent-$VER.war.asc
-mv continuum-buildagent-webapp-$VER.war.md5 apache-continuum-buildagent-$VER.war.md5
-mv continuum-buildagent-webapp-$VER.war.sha1 apache-continuum-buildagent-$VER.war.sha1
-
-mv continuum-buildagent-$VER.zip apache-continuum-buildagent-$VER-src.zip
-mv continuum-buildagent-$VER.zip.md5 apache-continuum-buildagent-$VER-src.zip.md5
-mv continuum-buildagent-$VER.zip.sha1 apache-continuum-buildagent-$VER-src.zip.sha1
-mv continuum-buildagent-$VER.zip.asc apache-continuum-buildagent-$VER-src.zip.asc
-
-script available with
-svn cat https://svn.apache.org/repos/asf/continuum/trunk/release-script.sh > release-script.sh
+svn cat http://svn.apache.org/repos/asf/continuum/trunk/release-script.sh > ../release-script.sh
+sh ../release-script.sh VERSION STAGING_URL
 +-----+
 
-~~  TODO:  copy and rename in one pass?
-
  [[1]] Stage the site <<<mvn site:stage-deploy -DstagingSiteURL=scp://people.apache.org/home/USERID/public_html/staging-sites/continuum/1.3.4>>> from the release tag or <<<target/checkout>>> directory
 
  [[1]] Call for a vote in the dev list and wait for 72 hours for the vote results. 3 binding votes from PMC members are necessary for the release to be finalized. <<{{{http://markmail.org/message/dhgdoz6aht6w5frl}Example}}>>