continuum-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wsm...@apache.org
Subject svn commit: r720970 - in /continuum/site/src/site/apt: development/release.apt guide-helping.apt
Date Wed, 26 Nov 2008 20:29:39 GMT
Author: wsmoak
Date: Wed Nov 26 12:29:38 2008
New Revision: 720970

URL: http://svn.apache.org/viewvc?rev=720970&view=rev
Log:
Add a page for the release process and guidelines.  Moved from wiki, still needs some editing.

Added:
    continuum/site/src/site/apt/development/release.apt
Modified:
    continuum/site/src/site/apt/guide-helping.apt

Added: continuum/site/src/site/apt/development/release.apt
URL: http://svn.apache.org/viewvc/continuum/site/src/site/apt/development/release.apt?rev=720970&view=auto
==============================================================================
--- continuum/site/src/site/apt/development/release.apt (added)
+++ continuum/site/src/site/apt/development/release.apt Wed Nov 26 12:29:38 2008
@@ -0,0 +1,211 @@
+ ------
+ 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.
+
+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 continuum-docs/src/site/xdoc/release-notes.xml
+
+  * copy and paste the html release notes from JIRA
+
+  * add <<<<h1>>>> around the first line
+
+  []
+
+ [[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.
+
++-----+
+<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.
+
+ #- Execute {{mvn release:prepare}} (check that it has been properly tagged. the tag name
must be.. <<<continuum-[VERSION]>>>)
+
+ #- Then execute {{mvn release:perform}}
+
+ # 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.0
+
+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
++-----+
+
+~~  TODO:  copy and rename in one pass?
+
+ # Stage the site {{mvn site:stage-deploy -DstagingSiteURL=scp://people.apache.org/home/USERID/staging-sites/continuum/1.2.2)}}
from the release tag or target/checkout directory
+
+ # Call for a vote in the dev list and wait for 72 hrs. for the vote results. 3 binding votes
from PMC members are necessary for the release to be finalized. [example|http://markmail.org/message/dhgdoz6aht6w5frl]
+
+ # After the vote has passed, copy the sources and binaries from {{people.apache.org}} to
{{/www/www.apache.org/dist/continuum}}.
+
+ # To sync the jars to ibiblio, 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=2.3 -DrepositoryId=apache.releases
++-----+
+
+ # Publish the docs wtih <<<mvn site-deploy>>> from the release tag
+
+ # Update the continuum site (https://svn.apache.org/repos/asf/continuum/site/) for the versions
and release notes
+ URL and run {{mvn site-deploy}}. Below are the list of pages that you need to update:
+
+ * <<<src/site/xdoc/index.xml>>>
+
+ * <<<src/site/apt/known-issues.apt>>>
+
+ * <<<src/site/apt/versions.apt>>>
+
+ * <<<src/site/apt/download.apt>>>
+
+ * <<<src/site/resources/.htaccess>>> - update
+ <<<Redirect Permanent /docs/current http://continuum.apache.org/docs/1.0.1/>>>
to the latest released GA version
+
+ []
+
+ # Remove old versions from {{/www/www.apache.org/dist/continuum}}
+
+ # 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}}
+
+ # 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.0/apache-continuum-1.3.0-bin.tar.gz
++-----+
+
+ Verify the signatures:
+
++-----+
+ gpg -v apache-continuum-1.3.0-bin.zip.asc
++-----+
+
+ Verify the checksums:
+
++-----+
+ md5sum apache-continuum-1.3.0-src.zip
+ cat apache-continuum-1.3.0-src.zip.md5
+
+ sha1sum apache-continuum-1.3.0-src.zip
+ cat apache-continuum-1.3.0-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.2.2/apache-continuum-1.2.2-bin* /www/www.apache.org/dist/continuum/binaries/
+cp /www/people.apache.org/builds/continuum/1.2.2/apache-continuum-1.2.2.war* /www/www.apache.org/dist/continuum/binaries/
+cp /www/people.apache.org/builds/continuum/1.2.2/apache-continuum-1.2.2-src* /www/www.apache.org/dist/continuum/source/
++-----+
+
+ Promote the staged repository contents
+
++-----+
+mvn stage:copy -Dsource="http://people.apache.org/builds/continuum/1.2.2/staging-repo" \
+-Dtarget="scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository"
\
+-Dversion=1.2.2 \
+-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
+
+ Publish the versioned reference docs (mvn site-deploy 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 verisons?)
+
+ Remove old releases from www.a.o/dist (make sure to remove them from downloads.apt or the
links will be broken)
+
+Releasing the parent pom
+
+ https://svn.apache.org/repos/asf/continuum/parent
+
+ - <<<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 of continuum -- https://svn.apache.org/repos/asf/continuum/trunk
(or branch)
+
+ - change the parent pom version to the {{continuum-parent}} version that has just been released
+
+ - commit the changes made

Modified: continuum/site/src/site/apt/guide-helping.apt
URL: http://svn.apache.org/viewvc/continuum/site/src/site/apt/guide-helping.apt?rev=720970&r1=720969&r2=720970&view=diff
==============================================================================
--- continuum/site/src/site/apt/guide-helping.apt (original)
+++ continuum/site/src/site/apt/guide-helping.apt Wed Nov 26 12:29:38 2008
@@ -63,6 +63,8 @@
 
   * {{{development/guide-continuum-development.html#Commit Message Template} Commit Message
Template}}
 
+  * {{{development/release.html}Release Process & Guidelines}}
+
 Resources for committers
 
   * {{{http://www.apache.org/dev/} Developer Resources}}



Mime
View raw message