Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9FFCFF138 for ; Fri, 29 Mar 2013 18:11:30 +0000 (UTC) Received: (qmail 68132 invoked by uid 500); 29 Mar 2013 18:11:30 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 67182 invoked by uid 500); 29 Mar 2013 18:11:14 -0000 Mailing-List: contact dev-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 dev@camel.apache.org Received: (qmail 66842 invoked by uid 99); 29 Mar 2013 18:11:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Mar 2013 18:11:02 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hzbarcea@gmail.com designates 209.85.160.175 as permitted sender) Received: from [209.85.160.175] (HELO mail-gh0-f175.google.com) (209.85.160.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Mar 2013 18:10:58 +0000 Received: by mail-gh0-f175.google.com with SMTP id f1so58987ghb.20 for ; Fri, 29 Mar 2013 11:10:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=X7azQSWL9JpckeUV6lUmSe09i0/ZcCxhB6rNMtK82xQ=; b=fDaKsqmtn84Ab5v+uQPaE354Ha7YGpVxGN9o5r0OyFNikQMD+t6i5w+tYAPaCIvQ4Y eIc5/h/bqXBXgViQxkIx6R6A4XEmN/jlWuEo3CBhYqWZcC7FI7UGtoJIP9bGJoVgXBGw 7xkzrh5W07FyskZjdfnTbC2QGRUSpK+2QuHBOo0X4Yb4T1XhMcj/ZdC6O2cbxmTN67WC 3M0r2pSOcwZoVSdbAl7Ha65H22vylQ2XbxKnkgea+LTGQ5fcftgKYmJAxEbza4NXt03j wAQVVkARO5oHPlVtIW5atM8uC9nN1XLNgtx3gTWGhLOrGqbVEOMj7ibdl5wqtj4592mY SPAQ== X-Received: by 10.236.199.78 with SMTP id w54mr1020974yhn.101.1364580637261; Fri, 29 Mar 2013 11:10:37 -0700 (PDT) Received: from [10.40.58.202] (cpe-107-015-170-016.nc.res.rr.com. [107.15.170.16]) by mx.google.com with ESMTPS id u19sm2439385yhh.15.2013.03.29.11.10.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 29 Mar 2013 11:10:36 -0700 (PDT) Message-ID: <5155D91B.3090608@gmail.com> Date: Fri, 29 Mar 2013 14:10:35 -0400 From: Hadrian Zbarcea User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: dev@camel.apache.org Subject: Re: [DISCUSS] - Moving towards Camel 2.11 release References: <51543506.5070100@gmail.com> In-Reply-To: <51543506.5070100@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org I have been advised to wait for the cxf-2.7.4 release, currently under vote. It has some rather important issues that we probably want to take. CXF committers on this list, please correct me if I am wrong. As there are already a number of positive votes, I expect the cxf release to become public on Mon, so I could build 2.11.0 on Tue. Cheers, Hadrian On 03/28/2013 08:18 AM, Hadrian Zbarcea wrote: > Christian, do you want to build this release or you want me to do it? > I'd also suggest doing a full build/test before the dryRun. > > Hadrian > > > > On 03/28/2013 05:22 AM, Christian M�ller wrote: >> Ok, I fixed [1] and removed it from the official Apache Camel SVN and >> update the docs. I will commit it into Camel Extra and add the docs there >> in a few minutes/hours. >> >> We only have two outstanding issues [2]. >> >> I will run a "mvn release:prepare -DdryRun=true" to check whether I hit >> some issues. >> Do we already have a release manager for Camel 2.11 (to make sure >> nobody is >> waiting for somebody)? >> >> [1] https://issues.apache.org/jira/browse/CAMEL-5483 >> [2] >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%222.11.0%22 >> >> >> Best, >> Christian >> >> On Thu, Mar 28, 2013 at 2:18 AM, Raul Kripalani wrote: >> >>> Hi, >>> >>> Managed to find time to commit the improvement for CAMEL-5698. >>> >>> For CAMEL-5916 the fix is almost ready. Hopefully I'll reach in time >>> before >>> we cut the release. It'll be a great improvement for the usability of >>> camel-cxfrs. >>> >>> Regards, >>> Ra�l. >>> >>> On Wed, Mar 27, 2013 at 1:30 PM, Claus Ibsen >>> wrote: >>> >>>> Hi >>>> >>>> Oh yeah and CAMEL-5483 is a issue we must resolve. I think Hadrian is >>>> working on that. >>>> >>>> >>>> On Wed, Mar 27, 2013 at 2:25 PM, Claus Ibsen >>>> wrote: >>>>> Hi >>>>> >>>>> Okay we are getting there. The JIRA tracker has 3 tickets for 2.11.0. >>>>> >>>> >>> https://issues.apache.org/jira/issues/?filter=12315472&jql=project%20%3D%20CAMEL%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%222.11.0%22 >>> >>>>> >>>>> And I think Willem have almost/done his 2 tickets. >>>>> >>>>> And the last ticket CAMEL-6042 requires some documentation about this >>>>> new functionality. I have asked Aaron to help with that. And it would >>>>> be great with a better set of unit tests as well. >>>>> >>>>> >>>>> -- >>>>> Claus Ibsen >>>>> ----------------- >>>>> Red Hat, Inc. >>>>> FuseSource is now part of Red Hat >>>>> Email: cibsen@redhat.com >>>>> Web: http://fusesource.com >>>>> Twitter: davsclaus >>>>> Blog: http://davsclaus.com >>>>> Author of Camel in Action: http://www.manning.com/ibsen >>>> >>>> >>>> >>>> -- >>>> Claus Ibsen >>>> ----------------- >>>> Red Hat, Inc. >>>> FuseSource is now part of Red Hat >>>> Email: cibsen@redhat.com >>>> Web: http://fusesource.com >>>> Twitter: davsclaus >>>> Blog: http://davsclaus.com >>>> Author of Camel in Action: http://www.manning.com/ibsen >>>> >>> >>