Return-Path: X-Original-To: apmail-servicemix-dev-archive@www.apache.org Delivered-To: apmail-servicemix-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 B499611059 for ; Mon, 14 Jul 2014 12:00:34 +0000 (UTC) Received: (qmail 80777 invoked by uid 500); 14 Jul 2014 12:00:34 -0000 Delivered-To: apmail-servicemix-dev-archive@servicemix.apache.org Received: (qmail 80740 invoked by uid 500); 14 Jul 2014 12:00:34 -0000 Mailing-List: contact dev-help@servicemix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@servicemix.apache.org Delivered-To: mailing list dev@servicemix.apache.org Received: (qmail 80729 invoked by uid 99); 14 Jul 2014 12:00:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2014 12:00:34 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [217.70.183.195] (HELO relay3-d.mail.gandi.net) (217.70.183.195) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2014 12:00:28 +0000 Received: from mfilter10-d.gandi.net (mfilter10-d.gandi.net [217.70.178.139]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id DACFAA80C4 for ; Mon, 14 Jul 2014 14:00:06 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter10-d.gandi.net Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by mfilter10-d.gandi.net (mfilter10-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id CO9g56kiGDcd for ; Mon, 14 Jul 2014 14:00:05 +0200 (CEST) X-Originating-IP: 78.244.148.153 Received: from [192.168.134.4] (ser34-1-78-244-148-153.fbx.proxad.net [78.244.148.153]) (Authenticated sender: jb@nanthrax.net) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 7887EA80C0 for ; Mon, 14 Jul 2014 14:00:05 +0200 (CEST) Message-ID: <53C3C645.1080604@nanthrax.net> Date: Mon, 14 Jul 2014 14:00:05 +0200 From: =?UTF-8?B?SmVhbi1CYXB0aXN0ZSBPbm9mcsOp?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: dev@servicemix.apache.org Subject: Re: Planning a 5.0.3 and 5.1.1 release? References: <53C3B54E.6060100@gmail.com> In-Reply-To: <53C3B54E.6060100@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org It sounds good to me. Karaf 2.3.6 and 2.4.0 should be available soon (something like beginning=20 of next week). Karaf 3.0.2 is planned just after (end of next week). regards JB On 07/14/2014 12:47 PM, Sobkowiak, Krzysztof wrote: > +1 for SMX 5.0.3 and 5.1.1 with current code base and 5.0.4 and 5.1.2 > with Karaf 2.3.6. > +1 for SMX 5.2.x with Karaf 2.4.0 > > With SMX 6 we should wait until Karaf 3.0.2 is available and contains > the fix for the deploy folder problem. > > Best regards > Krzysztof > > > On 14.07.2014 12:28, Gert Vanthienen wrote: >> L.S., >> >> >> It's not that a lot has happened on ServiceMix itself since the >> previous 5.0.2 and 5.1.0 releases, but the upgrades of Camel and CXF >> probably mean more to our user base than anything else. Doing a >> release isn't that much of an effort these days, so I think it makes >> sense to plan to do 5.0.3 and 5.1.1 release (perhaps later this week >> or early next week). Wdyt? >> >> Also, with a Karaf 2.4.0 in the works, we should probably also start >> getting ready to provide a corresponding ServiceMix release once >> that's out. In my mind, that's too big an upgrade to do in a >> micro/bugfix release, so perhaps we should set up a 5.2.x branch to >> work on that? >> >> >> Regards, >> >> Gert Vanthienen > --=20 Jean-Baptiste Onofr=C3=A9 jbonofre@apache.org http://blog.nanthrax.net Talend - http://www.talend.com