continuum-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From denn...@apache.org
Subject svn commit: r898080 - in /continuum/site/src/site/apt: community.apt development/building.apt development/debugging.apt development/guide-continuum-development.apt development/release.apt download.apt features.apt guide-helping.apt
Date Mon, 11 Jan 2010 21:47:03 GMT
Author: dennisl
Date: Mon Jan 11 21:47:02 2010
New Revision: 898080

URL: http://svn.apache.org/viewvc?rev=898080&view=rev
Log:
Fix typos and broken formating.
Add more formating.

Modified:
    continuum/site/src/site/apt/community.apt
    continuum/site/src/site/apt/development/building.apt
    continuum/site/src/site/apt/development/debugging.apt
    continuum/site/src/site/apt/development/guide-continuum-development.apt
    continuum/site/src/site/apt/development/release.apt
    continuum/site/src/site/apt/download.apt
    continuum/site/src/site/apt/features.apt
    continuum/site/src/site/apt/guide-helping.apt

Modified: continuum/site/src/site/apt/community.apt
URL: http://svn.apache.org/viewvc/continuum/site/src/site/apt/community.apt?rev=898080&r1=898079&r2=898080&view=diff
==============================================================================
--- continuum/site/src/site/apt/community.apt (original)
+++ continuum/site/src/site/apt/community.apt Mon Jan 11 21:47:02 2010
@@ -4,12 +4,12 @@
  Eric Redmond
  Emmanuel Venisse
  -----
- 17 October 2006
+ 2010-01-07
  -----
 
 The Continuum Community
 
-  Continuum, like any other opensource project, relies heavily on the efforts of the entire
user community
+  Continuum, like any other open source project, relies heavily on the efforts of the entire
user community
   to be ever vigilent for improvements, logging of defects, communicating use-cases, generating
   documentation, and being wary of other users in need. This is a quick guide outlining what
   members of the Continuum community may do to make the system work better for everyone.
@@ -27,7 +27,7 @@
 ** Help Log Defects in JIRA
 
   Just as any other healthy project requires a quick turn-around on defects, and a transparent
-  method of users to have their wishes heard, so too does Continuum need your help.
+  method for users to have their wishes heard, so too does Continuum need your help.
 
   * {{{http://jira.codehaus.org/browse/CONTINUUM}Continuum Defects, Improvements and Tasks}}
 

Modified: continuum/site/src/site/apt/development/building.apt
URL: http://svn.apache.org/viewvc/continuum/site/src/site/apt/development/building.apt?rev=898080&r1=898079&r2=898080&view=diff
==============================================================================
--- continuum/site/src/site/apt/development/building.apt (original)
+++ continuum/site/src/site/apt/development/building.apt Mon Jan 11 21:47:02 2010
@@ -1,100 +1,103 @@
- -------
- Building Continuum
- -------
-
-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
-  <<<continuum-jetty/target>>> and the war file in <<<continuum-webapp/target>>>.
-
-* 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 svn repo, there is a convenience 'all' directory with a 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 svn 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.3.x, from which we're publishing
-  miilestones.  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.2.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
+  <<<continuum-jetty/target>>> and the WAR file in <<<continuum-webapp/target>>>.
+
+* 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.

Modified: continuum/site/src/site/apt/development/debugging.apt
URL: http://svn.apache.org/viewvc/continuum/site/src/site/apt/development/debugging.apt?rev=898080&r1=898079&r2=898080&view=diff
==============================================================================
--- continuum/site/src/site/apt/development/debugging.apt (original)
+++ continuum/site/src/site/apt/development/debugging.apt Mon Jan 11 21:47:02 2010
@@ -1,6 +1,9 @@
  -----
  Debugging Continuum
  -----
+ ------
+ 2010-01-07
+ ------
 
 Debugging Continuum
 
@@ -20,20 +23,27 @@
 
  Now connect to the running instance with your debugger.
 
- For example, in Intellij IDEA:
+* Connecting with Intellij IDEA
 
- Run -> Edit Configurations
+** Configuration
 
- Press the '+' button to add a Configuration, and choose Remote
+ * Run -> Edit Configurations
 
- Give it a name, change the port to 8000, and save
+ * Press the '+' button to add a Configuration, and choose Remote
 
- To connect, choose Tools -> Run Debug,
- (or select your Configuration from the drop-down in the toolbar and click the Debug icon
next to it.)
+ * Give it a name, change the port to 8000, and click on OK
 
- To see what's happening behind the scenes, set a breakpoint in one of the Action classes,
which you'll find under
- src/main/java in the continuum-webapp module.
+ []
 
- Then visit http://localhost:9090 and navigate through the webapp until you hit the breakpoint
and your debugger takes
- over.
- 
\ No newline at end of file
+** Connection
+
+ * Choose Run -> Debug,
+ or select your Configuration from the drop-down in the toolbar and click the Debug icon
next to it
+
+ * To see what's happening behind the scenes, set a breakpoint in one of the Action classes,
which you'll find under
+ <<<src/main/java>>> in the <<<continuum-webapp>>> module
+
+ * Visit http://localhost:9090 and navigate through the webapp until you hit the breakpoint
and your debugger takes
+ over
+
+ []

Modified: continuum/site/src/site/apt/development/guide-continuum-development.apt
URL: http://svn.apache.org/viewvc/continuum/site/src/site/apt/development/guide-continuum-development.apt?rev=898080&r1=898079&r2=898080&view=diff
==============================================================================
--- continuum/site/src/site/apt/development/guide-continuum-development.apt (original)
+++ continuum/site/src/site/apt/development/guide-continuum-development.apt Mon Jan 11 21:47:02
2010
@@ -19,7 +19,7 @@
 
  * Name the file <<<CONTINUUM-<issue number>-<artifact id>.patch>>>.
 
- * Attach the patch to the JIRA issue you were working on (do not paste its content in as
a comment though). 
+ * Attach the patch to the JIRA issue you were working on (do not paste its content in as
a comment though).
    When adding the patch add a comment to the issue explaining what it does. Shortly after,
someone will apply the patch
    and close the issue.
 
@@ -33,7 +33,7 @@
 
  If you are picking up an issue with a existing patch attached to the issue you can apply
the patch to your working
  directory directly from JIRA like this. The <<<wget>>> and <<<patch>>>
commands will only be available if you are
- on a UNIX platform or using Cygwin on windows.
+ on a UNIX platform or using Cygwin on Windows.
 
 ---
 $ wget -O - -q <URL to the patch from JIRA> | patch -p0
@@ -128,11 +128,11 @@
   process and evaluate the change.
 
   <<Submitted by>> only needs to be included when a patch is being applied for
a non-committer.
-  
+
 eg:
 
 -----
 [CONTINUUM-1234] Fix X when doing Y
-Added a check to make sure Z is true before we decide to... This will prevent...  
+Added a check to make sure Z is true before we decide to... This will prevent...
 Submitted by: Baz Bazman
 -----

Modified: continuum/site/src/site/apt/development/release.apt
URL: http://svn.apache.org/viewvc/continuum/site/src/site/apt/development/release.apt?rev=898080&r1=898079&r2=898080&view=diff
==============================================================================
--- continuum/site/src/site/apt/development/release.apt (original)
+++ continuum/site/src/site/apt/development/release.apt Mon Jan 11 21:47:02 2010
@@ -1,261 +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 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]>>>)    
-
-+-----+
-Note: Scm tag does not work with Subversion > 1.5.1
-
-[1] Use subversion 1.4.1 or
-[2] 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
-+-----+
-
- #- 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.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?
-
- # 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
-
- # 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. <<{{{http://markmail.org/message/dhgdoz6aht6w5frl}Example}}>>
-
- # 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=1.3.4 -DrepositoryId=apache.releases
-+-----+
-
-    Note: Do not use Maven 2.0.9 because it has a bug when performing mvn stage:copy
-
- # execute fix permissions scripts. Login to people.apache.org
-
-+-----+
-/www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh
-+-----+
-
- # 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/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
-
- []
-
- # 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.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
-+-----+
-
-  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)
-
- Open a bottle of champaign ! :-)
-
-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
+ ------
+ 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 <<<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.
+
+ [[1]] Execute <<<mvn release:prepare>>> (check that it has been properly
tagged. The tag name must be <<<continuum-[VERSION]>>>)
+
+ <<Note:>> 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 <<<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
++-----+
+
+~~  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}}>>
+
+ [[1]] After the vote has passed, copy the sources and binaries from <<<people.apache.org>>>
to <<</www/www.apache.org/dist/continuum>>>.
+
+ [[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
++-----+
+
+    <<Note:>> Do not use Maven 2.0.9 because it has a bug when performing <<<mvn
stage:copy>>>
+
+ [[1]] Execute fix permissions scripts. Login to <<<people.apache.org>>>
+
++-----+
+/www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh
++-----+
+
+ [[1]] Publish the docs with <<<mvn site-deploy>>> 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:
+
+  * <<<src/site/xdoc/index.xml>>>
+
+  * <<<src/site/apt/known-issues.apt>>>
+
+  * <<<src/site/apt/versions.apt>>>
+
+  * <<<src/site/apt/download.apt>>>
+
+  * <<<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 old versions 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]] 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
++-----+
+
+ <<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 versions?)
+
+ Remove old releases from www.a.o/dist (make sure to remove them from <<<downloads.apt>>>
or the links will be broken)
+
+ Open a bottle of champagne ! :-)
+
+Releasing the parent POM
+
+ Check out the source from <<<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 in Continuum at <<<https://svn.apache.org/repos/asf/continuum/trunk>>>
(or in the 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/download.apt
URL: http://svn.apache.org/viewvc/continuum/site/src/site/apt/download.apt?rev=898080&r1=898079&r2=898080&view=diff
==============================================================================
--- continuum/site/src/site/apt/download.apt (original)
+++ continuum/site/src/site/apt/download.apt Mon Jan 11 21:47:02 2010
@@ -4,7 +4,8 @@
  Trygve Laugstol
  Emmanuel Venisse
  ------
- 2009-01-13
+ 2010-01-07
+ ------
 
 Download Apache Continuum
 
@@ -15,7 +16,7 @@
   Continuum 1.2.3 (GA) is distributed under the {{{http://continuum.apache.org/license.html}
Apache License, version 2.0}}.
 
   You will be prompted for a mirror - if the file is not found on yours, please be patient,
as it may take 24
-  hours to reach all mirrors.
+  hours for a new release to reach all mirrors.
 
 *-------------------------------+---------+----------+-----------+
 |                               | Download | Checksum | Signature |
@@ -96,5 +97,5 @@
 
  You can also verify the MD5 signature on the files. A Unix program called md5 or md5sum
is included in many
  Unix distributions. It is also available as part of {{{http://www.gnu.org/software/coreutils/}GNU
Coreutils}}.
- Windows users can get binary md5 programs from {{{http://www.fourmilab.ch/md5/}Fourmilab}},

+ Windows users can get binary md5 programs from {{{http://www.fourmilab.ch/md5/}Fourmilab}},
  {{{http://www.pc-tools.net/win32/freeware/console}PC-Tools}} or {{{http://www.slavasoft.com/fsum/}SlavaSoft}}.

Modified: continuum/site/src/site/apt/features.apt
URL: http://svn.apache.org/viewvc/continuum/site/src/site/apt/features.apt?rev=898080&r1=898079&r2=898080&view=diff
==============================================================================
--- continuum/site/src/site/apt/features.apt (original)
+++ continuum/site/src/site/apt/features.apt Mon Jan 11 21:47:02 2010
@@ -3,20 +3,20 @@
  ------
  Emmanuel Venisse
  ------
- Nov 15 2007
+ 2010-01-07
  ------
 
 Continuum Features
 
     Continuum offers the following features:
 
-    [[1]] <<Easy installation>> : Download the standalone application and run
it or deploy the Continuum war in your servlet container. {{{documentation/1_1/installation/index.html}Read
more}}
+    [[1]] <<Easy installation>> : Download the standalone application and run
it or deploy the Continuum WAR in your servlet container. {{{documentation/1_1/installation/index.html}Read
more}}
 
-    [[1]] <<Easy Configuration>> : Prjects builds are auto-configured but they
can be configured easily with the web interface
+    [[1]] <<Easy Configuration>> : Project's builds are auto-configured but they
can be configured easily with the web interface
 
     [[1]] <<SCM support>> : CVS, Subversion, Clearcase, Perforce, Starteam, Visual
Source Safe, CM Synergy, Bazaar, Mercurial are supported
 
-    [[1]] <<Change set support>> : For each build result, Continuum print all
scm changes ( commit authors, commit logs, modified files)
+    [[1]] <<Change set support>> : For each build result, Continuum print all
SCM changes (commit authors, commit logs, modified files)
 
     [[1]] <<Build notification>> : Mail, Jabber and Google Talk, MSN, IRC, report
deployment with wagon
 
@@ -30,6 +30,6 @@
 
     [[1]] <<Build queue>> : Users can view all projects in the queue and interrupt
some builds
 
-    [[1]] <<Distributed Builds>> : Projects can be distributed and built in multiple
build agents.
+    [[1]] <<Distributed Builds>> : Projects can be distributed and built in multiple
build agents
 
     [[1]] <<Parallel Builds>> : Projects can be built simultaneously or concurrently
locally using multiple build queues.

Modified: continuum/site/src/site/apt/guide-helping.apt
URL: http://svn.apache.org/viewvc/continuum/site/src/site/apt/guide-helping.apt?rev=898080&r1=898079&r2=898080&view=diff
==============================================================================
--- continuum/site/src/site/apt/guide-helping.apt (original)
+++ continuum/site/src/site/apt/guide-helping.apt Mon Jan 11 21:47:02 2010
@@ -5,7 +5,7 @@
  Jason van Zyl
  Emmanuel Venisse
  ------
- 12 October 2005
+ 2010-01-07
  ------
 
 Guide to helping with Continuum
@@ -54,7 +54,7 @@
  rights and nothing else is frowned upon, as is asking to be made a committer without having
contributed
  sufficiently to be invited.
 
-Developers Conventions
+Developer's Conventions
 
   There are a number of conventions used in the project, which contributors and developers
alike should follow for
   consistency's sake.



Mime
View raw message