Return-Path: Delivered-To: apmail-continuum-commits-archive@www.apache.org Received: (qmail 61057 invoked from network); 11 Jan 2010 21:51:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Jan 2010 21:51:54 -0000 Received: (qmail 89110 invoked by uid 500); 11 Jan 2010 21:51:54 -0000 Delivered-To: apmail-continuum-commits-archive@continuum.apache.org Received: (qmail 89062 invoked by uid 500); 11 Jan 2010 21:51:54 -0000 Mailing-List: contact commits-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@continuum.apache.org Delivered-To: mailing list commits@continuum.apache.org Received: (qmail 89053 invoked by uid 99); 11 Jan 2010 21:51:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jan 2010 21:51:54 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jan 2010 21:51:42 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id A9665238897D; Mon, 11 Jan 2010 21:51:20 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r898083 - in /continuum/site/src/site: apt/development/building.apt apt/development/debugging.apt apt/development/release.apt apt/events.apt cwiki/confluence-template.txt resources/.htaccess Date: Mon, 11 Jan 2010 21:51:20 -0000 To: commits@continuum.apache.org From: dennisl@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20100111215120.A9665238897D@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: dennisl Date: Mon Jan 11 21:51:20 2010 New Revision: 898083 URL: http://svn.apache.org/viewvc?rev=898083&view=rev Log: Set EOL-style to Native. Modified: continuum/site/src/site/apt/development/building.apt (contents, props changed) continuum/site/src/site/apt/development/debugging.apt (props changed) continuum/site/src/site/apt/development/release.apt (contents, props changed) continuum/site/src/site/apt/events.apt (props changed) continuum/site/src/site/cwiki/confluence-template.txt (contents, props changed) continuum/site/src/site/resources/.htaccess (props changed) Modified: continuum/site/src/site/apt/development/building.apt URL: http://svn.apache.org/viewvc/continuum/site/src/site/apt/development/building.apt?rev=898083&r1=898082&r2=898083&view=diff ============================================================================== --- continuum/site/src/site/apt/development/building.apt (original) +++ continuum/site/src/site/apt/development/building.apt Mon Jan 11 21:51:20 2010 @@ -1,103 +1,103 @@ - ------- - Building Continuum - ------- - ------ - 2010-01-07 - ------ - -Building Continuum - - This document will help you check out and build the Continuum source code. - -* Quick Start - -+--------+ - svn co http://svn.apache.org/repos/asf/continuum/all continuum-all - cd /path/to/continuum-all/parent - mvn install - cd /path/to/continuum-all/continuum - mvn install -+--------+ - - After a successful build, you will find the Continuum distributions in - <<>> and the WAR file in <<>>. - -* Maven - - To build Continuum, you will need {{{http://maven.apache.org/}Apache Maven}}. - {{{http://maven.apache.org/download.html}Download}} and {{{http://maven.apache.org/download.html#Installation} - install}} the the latest stable version. - -* Subversion - - The Continuum source code is stored in a {{{/source-repository.html}Subversion repository}} hosted by The - Apache Software Foundation. You will need a Subversion client in order to check out the source code. A list of - Subversion downloads and third-party clients is available on the {{{http://subversion.tigris.org/}Subversion}} web - site. - -* All - - In the Subversion repo, there is a convenience 'all' directory with an svn:externals definition that allows you to check out - the trunk, parent POM and site all at once. It will look empty when viewed in - your web browser, but checking it out with your Subversion client will bring down all - the code. - - {{{http://svn.apache.org/repos/asf/continuum/all} - http://svn.apache.org/repos/asf/continuum/all}} - -* Trunk - - The trunk of the Subversion repo has version 1.4.x, from which we're publishing - milestones. You can find more information about planned features on the - {{{http://cwiki.apache.org/confluence/display/CONTINUUM/Continuum+Roadmap}Roadmap}}. - If you see something interesting, please join us on the {{{/mail-lists.html}dev list}} to talk about it! - - {{{http://svn.apache.org/repos/asf/continuum/trunk} - http://svn.apache.org/repos/asf/continuum/trunk}} - -* Parent - - The Continuum parent POM contains configuration that is common to the entire - project. It has a separate, less frequent release cycle than the distribution. - - {{{http://svn.apache.org/repos/asf/continuum/parent/trunk} - http://svn.apache.org/repos/asf/continuum/parent/trunk}} - -* Site - - The source for the top-level Continuum website (including this page) is in a - separate directory in Subversion. It is published when changes are made, but - it is not tagged and "released". - - {{{http://svn.apache.org/repos/asf/continuum/site} - http://svn.apache.org/repos/asf/continuum/site}} - -* Branches - - We currently have one active release branch for 1.3.x bug fixes, - and several branches for ongoing work. Generally there will be some discussion - on the dev list or a JIRA issue opened before a branch is created. - - {{{http://svn.apache.org/repos/asf/continuum/branches} - http://svn.apache.org/repos/asf/continuum/branches}} - -* Sandbox - - The sandbox is an area where committers are free to experiment. No notice is - required to create something in the sandbox. - - {{{http://svn.apache.org/repos/asf/continuum/sandbox} - http://svn.apache.org/repos/asf/continuum/sandbox}} - -* Tags - - Tags for all past releases, test builds, and interesting points in time are - available. - - {{{http://svn.apache.org/repos/asf/continuum/tags} - http://svn.apache.org/repos/asf/continuum/tags}} - -* Help - - If you need help finding something or building it, please ask on the dev list - or on irc. + ------- + Building Continuum + ------- + ------ + 2010-01-07 + ------ + +Building Continuum + + This document will help you check out and build the Continuum source code. + +* Quick Start + ++--------+ + svn co http://svn.apache.org/repos/asf/continuum/all continuum-all + cd /path/to/continuum-all/parent + mvn install + cd /path/to/continuum-all/continuum + mvn install ++--------+ + + After a successful build, you will find the Continuum distributions in + <<>> and the WAR file in <<>>. + +* Maven + + To build Continuum, you will need {{{http://maven.apache.org/}Apache Maven}}. + {{{http://maven.apache.org/download.html}Download}} and {{{http://maven.apache.org/download.html#Installation} + install}} the the latest stable version. + +* Subversion + + The Continuum source code is stored in a {{{/source-repository.html}Subversion repository}} hosted by The + Apache Software Foundation. You will need a Subversion client in order to check out the source code. A list of + Subversion downloads and third-party clients is available on the {{{http://subversion.tigris.org/}Subversion}} web + site. + +* All + + In the Subversion repo, there is a convenience 'all' directory with an svn:externals definition that allows you to check out + the trunk, parent POM and site all at once. It will look empty when viewed in + your web browser, but checking it out with your Subversion client will bring down all + the code. + + {{{http://svn.apache.org/repos/asf/continuum/all} + http://svn.apache.org/repos/asf/continuum/all}} + +* Trunk + + The trunk of the Subversion repo has version 1.4.x, from which we're publishing + milestones. You can find more information about planned features on the + {{{http://cwiki.apache.org/confluence/display/CONTINUUM/Continuum+Roadmap}Roadmap}}. + If you see something interesting, please join us on the {{{/mail-lists.html}dev list}} to talk about it! + + {{{http://svn.apache.org/repos/asf/continuum/trunk} + http://svn.apache.org/repos/asf/continuum/trunk}} + +* Parent + + The Continuum parent POM contains configuration that is common to the entire + project. It has a separate, less frequent release cycle than the distribution. + + {{{http://svn.apache.org/repos/asf/continuum/parent/trunk} + http://svn.apache.org/repos/asf/continuum/parent/trunk}} + +* Site + + The source for the top-level Continuum website (including this page) is in a + separate directory in Subversion. It is published when changes are made, but + it is not tagged and "released". + + {{{http://svn.apache.org/repos/asf/continuum/site} + http://svn.apache.org/repos/asf/continuum/site}} + +* Branches + + We currently have one active release branch for 1.3.x bug fixes, + and several branches for ongoing work. Generally there will be some discussion + on the dev list or a JIRA issue opened before a branch is created. + + {{{http://svn.apache.org/repos/asf/continuum/branches} + http://svn.apache.org/repos/asf/continuum/branches}} + +* Sandbox + + The sandbox is an area where committers are free to experiment. No notice is + required to create something in the sandbox. + + {{{http://svn.apache.org/repos/asf/continuum/sandbox} + http://svn.apache.org/repos/asf/continuum/sandbox}} + +* Tags + + Tags for all past releases, test builds, and interesting points in time are + available. + + {{{http://svn.apache.org/repos/asf/continuum/tags} + http://svn.apache.org/repos/asf/continuum/tags}} + +* Help + + If you need help finding something or building it, please ask on the dev list + or on irc. Propchange: continuum/site/src/site/apt/development/building.apt ------------------------------------------------------------------------------ svn:eol-style = native Propchange: continuum/site/src/site/apt/development/debugging.apt ------------------------------------------------------------------------------ svn:eol-style = native Modified: continuum/site/src/site/apt/development/release.apt URL: http://svn.apache.org/viewvc/continuum/site/src/site/apt/development/release.apt?rev=898083&r1=898082&r2=898083&view=diff ============================================================================== --- continuum/site/src/site/apt/development/release.apt (original) +++ continuum/site/src/site/apt/development/release.apt Mon Jan 11 21:51:20 2010 @@ -1,266 +1,266 @@ - ------ - Continuum Release Guidelines - ------ - -Continuum Release Guidelines - - - * Continuum is versioned X.Y.Z -- Major.Minor.Build. The Major and Minor versions are set at the beginning of a - series, after which we use sequential build numbers starting with .0. For example, 1.3.0, 1.3.1, 1.3.2. - - * Ideally each version is tagged and built exactly once. The Release Manager (RM) has discretion to re-build a - version if something goes wrong during the release process, but once a version has been made available for public - download, that version number may not be re-used. - - * During the vote, an additional qualifier is determined. For example: 1.3.0 (M1) or 1.3.7 (GA). Respectively, - these mean Milestone 1 and General Availability. Qualifiers such as Alpha and Beta are also acceptable, as is RC - (Release Candidate). - - * If the vote does not pass, the qualifier may be reused. For example, if 1.3.0 was meant to be Milestone 1 but - does not get approved, 1.3.1 can become M1. - - * When releases are announced to the community, the additional qualifier is used in addition to the version number. - For example: [ANN] Continuum 1.3.3 (Milestone 2) Release or [ANN] Continuum 1.3.6 (GA) Release - - * A qualifier can be changed by calling a new vote. If we get to 1.3.8 (M5) and decide that it has no problems and - there's nothing else we want to add, we can simply re-label it GA and update the website. - - * New features may be added to 1.3.x releases until we reach GA, at which point only minor changes should be made. - - * If the vote does not pass, the binaries should be removed from the download area, and the version should be - labeled "test build" on the release notes page. - -Continuum Release Preparation - - [[1]] Post to the dev list a few days before you plan to do a Continuum release - - [[2]] Check for SNAPSHOT dependencies, including the Continuum parent POM - - [[1]] Update <<>> - - * Copy and paste the html release notes from JIRA - - * Add <<<\>>> around the first line - - [] - - [[1]] Update the <<>> for version changes - - [[1]] Make sure that you have the "release" profile set in your <<>> as shown below. - -+-----+ - - release - - [GPG_PASS_PHRASE] - - -+-----+ - - [[1]] Set your user credentials for the stage repo in the <<<>>> section of your <<>> file. - -Continuum Release Process - - By default, the release will be staged in <<>>. - If you want to stage it elsewhere, set the <<>> property in your <<>> file. - - [[1]] Execute <<>> (check that it has been properly tagged. The tag name must be <<>>) - - <> SCM tag does not work with Subversion \> 1.5.1 - - * Use subversion 1.4.1 or - - * 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. - -+-----+ -svn up -mvn release:prepare -+-----+ - - [] - - [[1]] Then execute <<>> - - [[1]] ssh to <<>> and cd to <<>>. 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 -+-----+ - -~~ TODO: copy and rename in one pass? - - [[1]] Stage the site <<>> from the release tag or <<>> 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}}>> - - [[1]] After the vote has passed, copy the sources and binaries from <<>> to <<>>. - - [[1]] To sync the JARs to the central repository, execute: - -+-----+ -mvn stage:copy -Dsource="[STAGE_REPO_URL]" - -Dtarget="scp://[APACHE_USERNAME]@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository" - -Dversion=1.3.4 -DrepositoryId=apache.releases -+-----+ - - <> Do not use Maven 2.0.9 because it has a bug when performing <<>> - - [[1]] Execute fix permissions scripts. Login to <<>> - -+-----+ -/www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh -+-----+ - - [[1]] Publish the docs with <<>> from the release tag - - [[1]] Update the Continuum site at <<>> with the versions and release notes - URL and run <<>>. Below is the list of pages that you need to update: - - * <<>> - - * <<>> - - * <<>> - - * <<>> - - * <<>> - - * <<>> - update - <<>> to the latest released GA version - - [] - - [[1]] Remove old versions from <<>> - - [[1]] Publish the reference docs (<<>> from the release tag. - You may have to exclude the <<>> module to do this, and will require <<>> - - [[1]] Send out an announcement of the release - -Verifying a Release - - Download the uploaded files via wget: - -+-----+ - wget http://people.apache.org/builds/continuum/1.3.4/apache-continuum-1.3.4-bin.tar.gz -+-----+ - - Verify the signatures: - -+-----+ - gpg -v apache-continuum-1.3.4-bin.zip.asc -+-----+ - - Verify the checksums: - -+-----+ - md5sum apache-continuum-1.3.4-src.zip - cat apache-continuum-1.3.4-src.zip.md5 - - sha1sum apache-continuum-1.3.4-src.zip - cat apache-continuum-1.3.4-src.zip.sha1 -+-----+ - -Publishing a release - - Tally the vote and reply on the vote thread. I prefer not to change the subject line as it breaks threading in some clients. - - Copy the distribution files over to www.a.o/dist/continuum - -+-----+ -cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-1.3.4-bin* /www/www.apache.org/dist/continuum/binaries/ -cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-1.3.4.war* /www/www.apache.org/dist/continuum/binaries/ -cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-1.3.4-src* /www/www.apache.org/dist/continuum/source/ -cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-buildagent-1.3.4-bin* /www/www.apache.org/dist/continuum/binaries/ -cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-buildagent-1.3.4.war* /www/www.apache.org/dist/continuum/binaries/ -cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-buildagent-1.3.4-src* /www/www.apache.org/dist/continuum/source/ -+-----+ - - Promote the staged repository contents - -+-----+ -mvn stage:copy -Dsource="http://people.apache.org/builds/continuum/1.3.4/staging-repo" \ --Dtarget="scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository" \ --Dversion=1.3.4 \ --DtargetRepositoryId=apache.releases -+-----+ - - <> This copies <> in the staging repo, even if you specify a version - - Update the <<>> and <<>> pages on the main site - - Publish the versioned reference docs (<<>> from a checkout of the tag) - - Publish the top-level website - - Announce the release on the dev and user lists - - Optionally announce on the Apache announcements list (only for major versions?) - - Remove old releases from www.a.o/dist (make sure to remove them from <<>> or the links will be broken) - - Open a bottle of champagne ! :-) - -Releasing the parent POM - - Check out the source from <<>> - - * <<>> (verify that it has been properly tagged) - - * <<>> (verify that it has been deployed correctly in the staging repo) - - * Update the parent POM version in Continuum at <<>> (or in the branch) - - * Change the parent POM version to the <<>> version that has just been released - - * Commit the changes made + ------ + Continuum Release Guidelines + ------ + +Continuum Release Guidelines + + + * Continuum is versioned X.Y.Z -- Major.Minor.Build. The Major and Minor versions are set at the beginning of a + series, after which we use sequential build numbers starting with .0. For example, 1.3.0, 1.3.1, 1.3.2. + + * Ideally each version is tagged and built exactly once. The Release Manager (RM) has discretion to re-build a + version if something goes wrong during the release process, but once a version has been made available for public + download, that version number may not be re-used. + + * During the vote, an additional qualifier is determined. For example: 1.3.0 (M1) or 1.3.7 (GA). Respectively, + these mean Milestone 1 and General Availability. Qualifiers such as Alpha and Beta are also acceptable, as is RC + (Release Candidate). + + * If the vote does not pass, the qualifier may be reused. For example, if 1.3.0 was meant to be Milestone 1 but + does not get approved, 1.3.1 can become M1. + + * When releases are announced to the community, the additional qualifier is used in addition to the version number. + For example: [ANN] Continuum 1.3.3 (Milestone 2) Release or [ANN] Continuum 1.3.6 (GA) Release + + * A qualifier can be changed by calling a new vote. If we get to 1.3.8 (M5) and decide that it has no problems and + there's nothing else we want to add, we can simply re-label it GA and update the website. + + * New features may be added to 1.3.x releases until we reach GA, at which point only minor changes should be made. + + * If the vote does not pass, the binaries should be removed from the download area, and the version should be + labeled "test build" on the release notes page. + +Continuum Release Preparation + + [[1]] Post to the dev list a few days before you plan to do a Continuum release + + [[2]] Check for SNAPSHOT dependencies, including the Continuum parent POM + + [[1]] Update <<>> + + * Copy and paste the html release notes from JIRA + + * Add <<<\>>> around the first line + + [] + + [[1]] Update the <<>> for version changes + + [[1]] Make sure that you have the "release" profile set in your <<>> as shown below. + ++-----+ + + release + + [GPG_PASS_PHRASE] + + ++-----+ + + [[1]] Set your user credentials for the stage repo in the <<<>>> section of your <<>> file. + +Continuum Release Process + + By default, the release will be staged in <<>>. + If you want to stage it elsewhere, set the <<>> property in your <<>> file. + + [[1]] Execute <<>> (check that it has been properly tagged. The tag name must be <<>>) + + <> SCM tag does not work with Subversion \> 1.5.1 + + * Use subversion 1.4.1 or + + * 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. + ++-----+ +svn up +mvn release:prepare ++-----+ + + [] + + [[1]] Then execute <<>> + + [[1]] ssh to <<>> and cd to <<>>. 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 ++-----+ + +~~ TODO: copy and rename in one pass? + + [[1]] Stage the site <<>> from the release tag or <<>> 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}}>> + + [[1]] After the vote has passed, copy the sources and binaries from <<>> to <<>>. + + [[1]] To sync the JARs to the central repository, execute: + ++-----+ +mvn stage:copy -Dsource="[STAGE_REPO_URL]" + -Dtarget="scp://[APACHE_USERNAME]@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository" + -Dversion=1.3.4 -DrepositoryId=apache.releases ++-----+ + + <> Do not use Maven 2.0.9 because it has a bug when performing <<>> + + [[1]] Execute fix permissions scripts. Login to <<>> + ++-----+ +/www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh ++-----+ + + [[1]] Publish the docs with <<>> from the release tag + + [[1]] Update the Continuum site at <<>> with the versions and release notes + URL and run <<>>. Below is the list of pages that you need to update: + + * <<>> + + * <<>> + + * <<>> + + * <<>> + + * <<>> + + * <<>> - update + <<>> to the latest released GA version + + [] + + [[1]] Remove old versions from <<>> + + [[1]] Publish the reference docs (<<>> from the release tag. + You may have to exclude the <<>> module to do this, and will require <<>> + + [[1]] Send out an announcement of the release + +Verifying a Release + + Download the uploaded files via wget: + ++-----+ + wget http://people.apache.org/builds/continuum/1.3.4/apache-continuum-1.3.4-bin.tar.gz ++-----+ + + Verify the signatures: + ++-----+ + gpg -v apache-continuum-1.3.4-bin.zip.asc ++-----+ + + Verify the checksums: + ++-----+ + md5sum apache-continuum-1.3.4-src.zip + cat apache-continuum-1.3.4-src.zip.md5 + + sha1sum apache-continuum-1.3.4-src.zip + cat apache-continuum-1.3.4-src.zip.sha1 ++-----+ + +Publishing a release + + Tally the vote and reply on the vote thread. I prefer not to change the subject line as it breaks threading in some clients. + + Copy the distribution files over to www.a.o/dist/continuum + ++-----+ +cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-1.3.4-bin* /www/www.apache.org/dist/continuum/binaries/ +cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-1.3.4.war* /www/www.apache.org/dist/continuum/binaries/ +cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-1.3.4-src* /www/www.apache.org/dist/continuum/source/ +cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-buildagent-1.3.4-bin* /www/www.apache.org/dist/continuum/binaries/ +cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-buildagent-1.3.4.war* /www/www.apache.org/dist/continuum/binaries/ +cp /www/people.apache.org/builds/continuum/1.3.4/apache-continuum-buildagent-1.3.4-src* /www/www.apache.org/dist/continuum/source/ ++-----+ + + Promote the staged repository contents + ++-----+ +mvn stage:copy -Dsource="http://people.apache.org/builds/continuum/1.3.4/staging-repo" \ +-Dtarget="scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository" \ +-Dversion=1.3.4 \ +-DtargetRepositoryId=apache.releases ++-----+ + + <> This copies <> in the staging repo, even if you specify a version + + Update the <<>> and <<>> pages on the main site + + Publish the versioned reference docs (<<>> from a checkout of the tag) + + Publish the top-level website + + Announce the release on the dev and user lists + + Optionally announce on the Apache announcements list (only for major versions?) + + Remove old releases from www.a.o/dist (make sure to remove them from <<>> or the links will be broken) + + Open a bottle of champagne ! :-) + +Releasing the parent POM + + Check out the source from <<>> + + * <<>> (verify that it has been properly tagged) + + * <<>> (verify that it has been deployed correctly in the staging repo) + + * Update the parent POM version in Continuum at <<>> (or in the branch) + + * Change the parent POM version to the <<>> version that has just been released + + * Commit the changes made Propchange: continuum/site/src/site/apt/development/release.apt ------------------------------------------------------------------------------ svn:eol-style = native Propchange: continuum/site/src/site/apt/events.apt ------------------------------------------------------------------------------ svn:eol-style = native Modified: continuum/site/src/site/cwiki/confluence-template.txt URL: http://svn.apache.org/viewvc/continuum/site/src/site/cwiki/confluence-template.txt?rev=898083&r1=898082&r2=898083&view=diff ============================================================================== --- continuum/site/src/site/cwiki/confluence-template.txt (original) +++ continuum/site/src/site/cwiki/confluence-template.txt Mon Jan 11 21:51:20 2010 @@ -1,94 +1,94 @@ - - - - - $page.title - - - - - - - - - -
- -
-
-
- -
- $body -
- -
-
-
-
-
- - - + + + + + $page.title + + + + + + + + + +
+ +
+
+
+ +
+ $body +
+ +
+
+
+
+
+ + + Propchange: continuum/site/src/site/cwiki/confluence-template.txt ------------------------------------------------------------------------------ svn:eol-style = native Propchange: continuum/site/src/site/resources/.htaccess ------------------------------------------------------------------------------ svn:eol-style = native