Return-Path: X-Original-To: apmail-continuum-commits-archive@www.apache.org Delivered-To: apmail-continuum-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1F7EB9589 for ; Wed, 2 Jan 2013 06:02:09 +0000 (UTC) Received: (qmail 82961 invoked by uid 500); 2 Jan 2013 06:02:08 -0000 Delivered-To: apmail-continuum-commits-archive@continuum.apache.org Received: (qmail 82935 invoked by uid 500); 2 Jan 2013 06:02:08 -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 82924 invoked by uid 99); 2 Jan 2013 06:02:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jan 2013 06:02:08 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.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; Wed, 02 Jan 2013 06:01:58 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 19EAE2388980; Wed, 2 Jan 2013 06:01:36 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1427661 [1/2] - in /continuum/site-publish: ./ development/ images/ Date: Wed, 02 Jan 2013 06:01:34 -0000 To: commits@continuum.apache.org From: brett@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20130102060136.19EAE2388980@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: brett Date: Wed Jan 2 06:01:34 2013 New Revision: 1427661 URL: http://svn.apache.org/viewvc?rev=1427661&view=rev Log: Site checkin for project Continuum Modified: continuum/site-publish/articles.html continuum/site-publish/change-log.html continuum/site-publish/community.html continuum/site-publish/development/building.html continuum/site-publish/development/debugging.html continuum/site-publish/development/guide-continuum-development.html continuum/site-publish/development/release.html continuum/site-publish/download.html continuum/site-publish/error-states.html continuum/site-publish/events.html continuum/site-publish/faqs.html continuum/site-publish/features.html continuum/site-publish/getting-help.html continuum/site-publish/guide-helping.html continuum/site-publish/images/continuum_logo_75.gif continuum/site-publish/index.html continuum/site-publish/issue-tracking.html continuum/site-publish/known-issues.html continuum/site-publish/license.html continuum/site-publish/mail-lists.html continuum/site-publish/privacy-policy.html continuum/site-publish/project-info.html continuum/site-publish/security.html continuum/site-publish/source-repository.html continuum/site-publish/team-list.html Modified: continuum/site-publish/articles.html URL: http://svn.apache.org/viewvc/continuum/site-publish/articles.html?rev=1427661&r1=1427660&r2=1427661&view=diff ============================================================================== --- continuum/site-publish/articles.html (original) +++ continuum/site-publish/articles.html Wed Jan 2 06:01:34 2013 @@ -115,6 +115,10 @@ pageTracker._trackPageview();
  • Live Demo
  • + +
  • + Security +
  • Community
    Continuum Development
    @@ -211,11 +223,12 @@ pageTracker._trackPageview();

    By defa



    Modified: continuum/site-publish/development/guide-continuum-development.html URL: http://svn.apache.org/viewvc/continuum/site-publish/development/guide-continuum-development.html?rev=1427661&r1=1427660&r2=1427661&view=diff ============================================================================== --- continuum/site-publish/development/guide-continuum-development.html (original) +++ continuum/site-publish/development/guide-continuum-development.html Wed Jan 2 06:01:34 2013 @@ -115,6 +115,10 @@ pageTracker._trackPageview();
  • Live Demo
  • + +
  • + Security +
  • Community
    Continuum Development
    @@ -222,11 +234,12 @@ Submitted by: Baz Bazman

    Modified: continuum/site-publish/development/release.html URL: http://svn.apache.org/viewvc/continuum/site-publish/development/release.html?rev=1427661&r1=1427660&r2=1427661&view=diff ============================================================================== --- continuum/site-publish/development/release.html (original) +++ continuum/site-publish/development/release.html Wed Jan 2 06:01:34 2013 @@ -114,6 +114,10 @@ pageTracker._trackPageview();
  • Live Demo
  • + +
  • + Security +
  • Community
    Continuum Development
    @@ -205,7 +217,7 @@ pageTracker._trackPageview();

    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 relea se
    2. Check for SNAPSHOT dependencies, including the Continuum parent POM
    3. Update continuum-docs/src/site/xdoc/release-notes.xml
      • Copy and paste the html release notes from JIRA
      • Remove the first line with the heading

    Continuum Release Process

    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:
      mvn clean install -Pintegration
    2. Execute mvn release:prepare (check that it has been properly tagged. The tag name must be continuum-[VERSION])
    3. Then execute mvn release:perform
    4. Copy the release artifacts from the Archiva repository to the Continuum distribution testing area ~~ TODO: expand with instructions for pubsub
    5. Stage the site mvn -Ptag site-deploy from the continuum-docs module of the release tag or target/checkout directory
    6. 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. Example.
    7. After the vote has passed, copy the sources and binaries to the production Continuum distribution area ~~ TODO: expand with instructions for pubsub
    8. Remove versions that no longer need to be downloaded from mirrors ~~ TODO: expand with instruct ions for pubsub
    9. 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: You can also use scpexe:// especially if you are building from another machine using SSH agent forwarding

    10. Execute fix permissions scripts. Login to people.apache.org
      /www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh
    11. 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/download.apt
      • src/site/apt/changelog.apt
    12. Publish the reference docs (mvn site site:stage scmpublish:publish-scm from the release tag or previous target/checkout directory.
    13. Update JIRA to indicate the version is released
    14. 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:

     wget http://people.apache.org/builds/continuum/1.3.4/source/apache-continuum-1.3.4-src.tar.gz

    Verify the signatures:

     gpg -v apache-continuum-1.3.4-src.zip.asc

    Verify the checksums:

     openssl md5 apache-continuum-1.3.4-src.zip
    +     -Dversion=1.3.4 -DrepositoryId=apache.releases

    Note: You can also use scpexe:// especially if you are building from another machine using SSH agent forwarding

  • Execute fix permissions scripts. Login to people.apache.org
    /www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh
  • 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/download.apt
    • src/site/apt/changelog.apt
  • Publish the reference docs (mvn site site:stage scm-publish:publish-scm from the release tag or previous target/checkout directory.
  • Update JIRA to indicate the version is release d
  • 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:

     wget http://people.apache.org/builds/continuum/1.3.4/source/apache-continuum-1.3.4-src.tar.gz

    Verify the signatures:

     gpg -v apache-continuum-1.3.4-src.zip.asc

    Verify the checksums:

     openssl md5 apache-continuum-1.3.4-src.zip
      cat apache-continuum-1.3.4-src.zip.md5
     
      openssl sha1 apache-continuum-1.3.4-src.zip
    @@ -216,11 +228,12 @@ pageTracker._trackPageview();
           
    -

    Download Apache Continuum

    Previous Releases

    More releases are available in the Apache Continuum Archives or prior to the graduation from Maven, in the Apache Maven Archives.

    Verify the integrity of the files

    We recommend that you verify the integrity of the downloaded files using the PGP signatures and MD5 checksums.

    The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the asc signature file for the particular distribution. Make sure you get these files from the main distribution directory, rather than from a mirror. Then verify the signatures using

    % pgpk -a KEYS

    % pgpv $filename.tar.gz.asc

    or

    % pgp -ka KEYS

    % pgp $filename.tar.gz.asc

    or

    % gpg --import KEYS

    % gpg --verify $filename.tar.gz.asc

    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 GNU Coreutils. Windows users can get binary md5 programs from Fourmilab, PC-Tools or SlavaSoft.

    +

    Download Apache Continuum

    Apache Continuum is an enterprise-ready continuous integration server with features such as automated builds, release management, role-based security, and integration with popular build tools and source control management systems. Whether you have a centralized build team or want to put control of releases in the hands of developers, Continuum can help you improve quality and maintain a consistent build environment.

    Previous Releases

    More releases are available in the Apache Continuum Archives or prior to the graduation from Maven, in the Apache Maven Archives.

    Verify the integrity of the files

    We recommend that you verify the integrity of the downloaded files using the PGP signatures and MD5 checksums.

    The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the asc signature file for the particular distribution. Make sure you get these files from the main distribution directory, rather than from a mirror. Then verify the signatures using

    % pgpk -a KEYS

    % pgpv $filename.tar.gz.asc

    or

    % pgp -ka KEYS

    % pgp $filename.tar.gz.asc

    or

    % gpg --import KEYS

    % gpg --verify $filename. tar.gz.asc

    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 GNU Coreutils. Windows users can get binary md5 programs from Fourmilab, PC-Tools or SlavaSoft.