Return-Path: X-Original-To: apmail-camel-commits-archive@www.apache.org Delivered-To: apmail-camel-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 BFE02189DF for ; Thu, 29 Oct 2015 21:18:48 +0000 (UTC) Received: (qmail 23654 invoked by uid 500); 29 Oct 2015 21:18:48 -0000 Delivered-To: apmail-camel-commits-archive@camel.apache.org Received: (qmail 23606 invoked by uid 500); 29 Oct 2015 21:18:48 -0000 Mailing-List: contact commits-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list commits@camel.apache.org Received: (qmail 23597 invoked by uid 99); 29 Oct 2015 21:18:48 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Oct 2015 21:18:48 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 2AAB81A24DB for ; Thu, 29 Oct 2015 21:18:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.791 X-Spam-Level: * X-Spam-Status: No, score=1.791 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id KAsodkfYPXpQ for ; Thu, 29 Oct 2015 21:18:46 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTP id A21AC21342 for ; Thu, 29 Oct 2015 21:18:46 +0000 (UTC) Received: from svn01-us-west.apache.org (svn.apache.org [10.41.0.6]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 411FDE0451 for ; Thu, 29 Oct 2015 21:18:46 +0000 (UTC) Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id 3F34D3A0289 for ; Thu, 29 Oct 2015 21:18:46 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r970688 - in /websites/production/camel/content: cache/main.pageCache release-guide.html Date: Thu, 29 Oct 2015 21:18:46 -0000 To: commits@camel.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20151029211846.3F34D3A0289@svn01-us-west.apache.org> Author: buildbot Date: Thu Oct 29 21:18:46 2015 New Revision: 970688 Log: Production update by buildbot for camel Modified: websites/production/camel/content/cache/main.pageCache websites/production/camel/content/release-guide.html Modified: websites/production/camel/content/cache/main.pageCache ============================================================================== Binary files - no diff available. Modified: websites/production/camel/content/release-guide.html ============================================================================== --- websites/production/camel/content/release-guide.html (original) +++ websites/production/camel/content/release-guide.html Thu Oct 29 21:18:46 2015 @@ -186,7 +186,7 @@ Certificate information: Fingerprint: bc:5f:40:92:fd:6a:49:aa:f8:b8:35:0d:ed:27:5e:a6:64:c1:7a:1b (R)eject, accept (t)emporarily or accept (p)ermanently? -

Copy $CAMEL_ROOT/trunk/etc/scripts/release-website.sh to your home directory on people.apache.org
Execute this script, e.g: ./release-website.sh 2.10.0
1. It will download the XML Schema files and the Camel manual for the given release version
2. At the end you have to commit these changes manually to SVN (simply follow the instructions)

Update the Xml Reference page with a link to the XSD's

Update the Manual page with a link to the PDF/HTML if it's a new major/minor version

Mail the dev, user & announce lists

Post a news entry in the wiki which links to the release page so folks can download it!

perform a full export of the Camel WIKI sites to see your blog on the Camel index site. To do this, you have to remove the main.pageCache file in the content/cache sub directory:

execute: svn rm https://svn.apache.org/repos/infra/websites/production/camel/content/cache/main.pageCache

Add the release version number to the following spring.schemas file located in src/main/resources/META-INF directory of the following components:
camel-cxf
camel-spring
camel-spring-integration
camel-spring-security

Have a beer!

Create a new maintenance branch

This section is out of date.

This section just for creating a maintenance branch in camel svn repo, it is much easy to create a new branch after camel repo is switched to Git.

When we finish the major version release, we need to create a maintenance branch to holds the bug fixes. Here are the steps for it.

Create a branch from trunk remotely
+
Update the Xml Reference page with a link to the XSD's
Update the Manual page with a link to the PDF/HTML if it's a new major/minor version
Mail the dev, user & announce lists
Post a news entry in the wiki which links to the release page so folks can download it!
perform a full export of the Camel WIKI sites to see your blog on the Camel index site. To do this, you have to remove the main.pageCache file in the content/cache sub directory:
1. execute: svn rm https://svn.apache.org/repos/infra/websites/production/camel/content/cache/main.pageCache
Add the release version number to the following spring.schemas file located in src/main/resources/META-INF directory of the following components:
camel-cxf
camel-spring
camel-spring-integration
camel-spring-security
Have a beer!

Create a new maintenance branch

This section is out of date.

This section just for creating a maintenance branch in camel svn repo, it is much easy to create a new branch after camel repo is switched to Git.

When we finish the major version release, we need to create a maintenance branch to holds the bug fixes. Here are the steps for it.

Create a branch from trunk remotely

Check out the remote branch in a new directory