continuum-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From br...@apache.org
Subject svn commit: r1427634 - in /continuum/site/src/site: apt/development/release.apt resources/.htaccess
Date Wed, 02 Jan 2013 03:41:32 GMT
Author: brett
Date: Wed Jan  2 03:41:31 2013
New Revision: 1427634

URL: http://svn.apache.org/viewvc?rev=1427634&view=rev
Log:
update the release guidelines (some information still needs adjusting as
current release progresses)

Removed:
    continuum/site/src/site/resources/.htaccess
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=1427634&r1=1427633&r2=1427634&view=diff
==============================================================================
--- continuum/site/src/site/apt/development/release.apt (original)
+++ continuum/site/src/site/apt/development/release.apt Wed Jan  2 03:41:31 2013
@@ -44,29 +44,13 @@ Continuum Release Preparation
 
   []
 
- [[1]] Make sure that you have the "release" profile set in your <<<settings.xml>>>
as shown below.
-
-+-----+
-<profile>
-  <id>release</id>
-  <properties>
-    <gpg.passphrase>[GPG_PASS_PHRASE]</gpg.passphrase>
-  </properties>
-</profile>
-+-----+
-
- [[1]] Set your user credentials for the stage repo in the <<<<servers>>>>
section of your <<<settings.xml>>> file.
-
 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. For example:
-
-----
-<deploy.altRepository>vmbuild.staging::default::http://vmbuild.apache.org/archiva/repository/staged-continuum/</deploy.altRepository>
-----
-
-  <Note:> If using Archiva to deploy to, you will need to clear the deployment repository
first
+ The release will be staged in 
+ {{https://archiva-repository.apache.org/archiva/repository/continuum-releases/}}.
+ You will need to set your user credentials for the Archiva repository in the
+  <<<<servers>>>> section of your <<<settings.xml>>>
file, under the
+  <<<archiva-repository.releases>>> server ID.
 
  [[1]] Check trunk is building correctly (including Selenium tests) by running:
 
@@ -78,18 +62,20 @@ mvn clean install -Pintegration
 
  [[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.
+ [[1]] Copy the release artifacts from the Archiva repository to the Continuum distribution
testing area ~~ TODO: expand with instructions for pubsub
 
-+-----+
-svn cat http://svn.apache.org/repos/asf/continuum/project/release-script.sh > ../release-script.sh
-sh ../release-script.sh VERSION STAGING_URL
-+-----+
+ [[1]] Stage the site <<<mvn -Ptag site-deploy>>> from the 
+       <<<continuum-docs>>> module of the release tag or 
+       <<<target/checkout>>> directory
 
- [[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 <<<continuum-docs>>> module of 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}}>>. 
 
- [[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 to the production Continuum
distribution area ~~ TODO: expand with instructions for pubsub
 
- [[1]] After the vote has passed, copy the sources and binaries from <<<people.apache.org>>>
to <<</www/www.apache.org/dist/continuum>>>.
+ [[1]] Remove versions that no longer need to be downloaded from mirrors ~~ TODO: expand
with instructions for pubsub
 
  [[1]] To sync the JARs to the central repository, execute:
 
@@ -99,8 +85,6 @@ mvn stage:copy -Dsource="[STAGE_REPO_URL
      -Dversion=1.3.4 -DrepositoryId=apache.releases
 +-----+
 
-    <<Note:>> Do not use Maven 2.0.9 because it has a bug when performing <<<mvn
stage:copy>>>
-
     <<Note:>> You can also use scpexe:// especially if you are building from
another machine using SSH agent forwarding
 
  [[1]] Execute fix permissions scripts. Login to <<<people.apache.org>>>
@@ -109,8 +93,6 @@ mvn stage:copy -Dsource="[STAGE_REPO_URL
 /www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh
 +-----+
 
- [[1]] Publish the docs with <<<mvn site-deploy>>> from the <<<continuum-docs>>>
module from the release tag
-
  [[1]] Update the Continuum site at <<<https://svn.apache.org/repos/asf/continuum/site/>>>
with the versions and release notes
  URL and run <<<mvn site-deploy>>>. Below is the list of pages that you
need to update:
 
@@ -122,24 +104,23 @@ mvn stage:copy -Dsource="[STAGE_REPO_URL
 
   * <<<src/site/apt/changelog.apt>>>
 
-  * <<<src/site/resources/.htaccess>>> - update
-  <<<Redirect Permanent /docs/current http://continuum.apache.org/docs/1.0.1/>>>
to the latest released GA version
-
   []
 
- [[1]] Remove versions that no longer need to be downloaded from the mirror from <<</www/www.apache.org/dist/continuum>>>
-
- [[1]] Publish the reference docs (<<<mvn site-deploy>>> from the release
tag.
- You may have to exclude the <<<continuum-webapp>>> module to do this,
and will require <<<MAVEN_OPTS=-Xmx256m>>>
+ [[1]] Publish the reference docs 
+       (<<<mvn site site:stage scmpublish:publish-scm>>> from the release
tag
+       or previous <<<target/checkout>>> directory.
 
  [[1]] Update JIRA to indicate the version is released
 
- [[1]] Send out an announcement of the release
+ [[1]] Send out an announcement of the release to users@continuum.apache.org,
+       and announce@apache.org (for GA releases). This must be sent from your
+       @apache.org address.
 
 Verifying a Release
 
  Download the uploaded files via wget:
 
+~~ TODO: adjust for pubsub
 +-----+
  wget http://people.apache.org/builds/continuum/1.3.4/source/apache-continuum-1.3.4-src.tar.gz
 +-----+
@@ -153,62 +134,46 @@ Verifying a Release
  Verify the checksums:
 
 +-----+
- md5sum apache-continuum-1.3.4-src.zip
+ openssl md5 apache-continuum-1.3.4-src.zip
  cat apache-continuum-1.3.4-src.zip.md5
 
- sha1sum apache-continuum-1.3.4-src.zip
+ openssl sha1 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/www.apache.org/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/
-+-----+
-
- 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
-+-----+
-
- <<Note:>>  This copies <<everything>> in the staging repo, even
if you specify a version
-
- Update the <<<index.xml>>> and <<<downloads.apt>>> pages
on the main site
+Releasing the parent POM
 
- Publish the versioned reference docs (<<<mvn site-deploy>>> from a checkout
of the tag)
+ Check out the source from <<<https://svn.apache.org/repos/asf/continuum/parent>>>
 
- Publish the top-level website
+ * <<<mvn release:prepare>>> (verify that it has been properly tagged)
 
- Announce the release on the dev and user lists
+ * <<<mvn release:perform>>> (verify that it has been deployed correctly
in the staging repo)
 
- Optionally announce on the Apache announcements list (only for major versions?)
+ * Conduct a vote (or do it in conjunction with a Continuum release)
 
- Remove old releases from /www/www.apache.org/dist (make sure to remove them from <<<downloads.apt>>>
or the links will be broken)
+ * Update the parent POM version in Continuum at
+   <<<https://svn.apache.org/repos/asf/continuum/trunk>>> (or in the branch),
+   in the site at
+   <<<https://svn.apache.org/repos/asf/continuum/site>>>, and the skin
at
+   <<<https://svn.apache.org/repos/asf/continuum/skin/trunk>>> to change
the
+   parent POM version to the <<<continuum-parent>>> version that has just

+   been released
 
- Open a bottle of champagne ! :-)
+ * Commit the changes made
 
-Releasing the parent POM
+Releasing the Site Skin
 
- Check out the source from <<<https://svn.apache.org/repos/asf/continuum/parent>>>
+ Check out the source from
+ <<<https://svn.apache.org/repos/asf/continuum/skin/trunk>>>
 
  * <<<mvn release:prepare>>> (verify that it has been properly tagged)
 
  * <<<mvn release:perform>>> (verify that it has been deployed correctly
in the staging repo)
 
- * Update the parent POM version in Continuum at <<<https://svn.apache.org/repos/asf/continuum/trunk>>>
(or in the branch)
+ * Conduct a vote (or do it in conjunction with a Continuum release)
 
- * Change the parent POM version to the <<<continuum-parent>>> version
that has just been released
+ * Update the <<<site.xml>>> in Continuum at 
+   <<<https://svn.apache.org/repos/asf/continuum/trunk>>> and in the site
at
+   <<<https://svn.apache.org/repos/asf/continuum/site>>>
 
  * Commit the changes made



Mime
View raw message