You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Krzysztof Sobkowiak <kr...@gmail.com> on 2014/10/09 17:02:37 UTC

[DISCUSS] ServiceMix 5.3..x plans (was: Re: Release Schedule and request for release update using Karaf 2.4.0)

Hi

Do you have any idea how to solve this problem. As discussed in Irc we
have 2 possible solutions (both have pros and cons)

  * we can create a new branch for distribution based on Karaf 2.4.x and
    Camel 2.13.x, but in this case we will have one mor branch to maintain
  * wen can do 5.3.0 with Karaf 2.4.0 and Camel 2.13.x as pre-release
    and next 5.3.1+ with Camel 2.14.x to let people smooth transition
    from Karaf 2.3.x and Camel 2.14.x

Wdyt?

Regards
Krzysztof



-------- Original Message --------
Subject: 	Re: Release Schedule and request for release update using
Karaf 2.4.0
Date: 	Thu, 9 Oct 2014 14:30:20 +0200
From: 	Michael Täschner <m....@gmail.com>
Reply-To: 	users@servicemix.apache.org
To: 	users@servicemix.apache.org



Hi Krzysztof,

thanks for the release schedule overview. Do you see any chance for the
combination of Karaf 2.4.0 + Camel 2.13.2 because incrementing directly to
Camel 2.14.0 will have big impact on our customized container where I have
to verify that every CXF interceptor we provide with the container (service
monitoring, statistics) will have to be tested with the major CXF release
change to 3.0.2?

If not, do you have any recommendation how I could easily exchange the
karaf version only based on my ServiceMix 5.1.x build ?

I will of course also look into taking the plunge towards ServiceMix 5.3 as
well ...

Cheers,
Michael

2014-10-07 18:51 GMT+02:00 Krzysztof Sobkowiak <kr...@gmail.com>:

> Hi Michael
>
> I have created initial version of the roadmap page. You can find it
> here  http://servicemix.apache.org/community/releases-schedule.html
>
> Best regards
> Krzysztof
>
> On 22.09.2014 11:16, Michael Täschner wrote:
> > Hi,
> >
> > I have two questions regarding the servicemix roadmap ?
> > - Is there a overview page with servicemix roadmap similar to karaf (
> > http://karaf.apache.org/index/community/releases-schedule.html) ?
> > - Do you see a chance to prepare a 5.2.0 release with upgrade to Karaf
> > 2.4.0 ? I am really looking forward to updating to servlet-api 3.0 which
> is
> > provided by pax-web 3.x (contained in Karaf 2.4.0) and used by various
> > camel components (camel:websocket, camel:cxf, etc.)
> >
> > Thanks and Regards,
> > Michael
> >
>
>
> --
> Krzysztof Sobkowiak
>
> JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
> @ ASF
> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
> <http://www.pl.capgemini-sdm.com/> | Wroclaw
> e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
> Twitter: @KSobkowiak
> Calendar: http://goo.gl/yvsebC
>




Re: [DISCUSS] ServiceMix 5.3..x plans

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Go ahead, no problem for me.

Thanks,
Regards
JB

On 10/10/2014 05:55 PM, Krzysztof Sobkowiak wrote:
> So, if no veto I would cut 5.3.0 next.
>
> Regards
> Krzysztof
>
> On 09.10.2014 22:02, Gert Vanthienen wrote:
>> L.S.,
>>
>> Yeah, that would be my preference:
>>   * a 5.2.x branch with Karaf 2.3.x and Camel 2.14.x
>>   * a 5.3.x branch with Karaf 2.4.x and Camel 2.13.x
>>   * a 5.4.x branch with Karaf 2.4.x and Camel 2.14.x
>>
>> I think we're considering to do those releases (with those
>> combinations of Karaf/Camel) anyway, so the only question is whether
>> or not we create a separate branch for the 5.3.x and 5.4.x releases.
>> In my mind, it would make sense to have a separate branch for those
>> two, even if we only do 5.3.0 release off the 5.3.x branch and then
>> move straight to 5.4.0. Just my 2 cents though...
>>
>> Regards,
>>
>> Gert Vanthienen
>>
>>
>> On Thu, Oct 9, 2014 at 9:24 PM, Krzysztof Sobkowiak
>> <kr...@gmail.com> wrote:
>>> My mistake:
>>>
>>>    * 5.2.x with Karaf 2.3.x and Camel 2.14.x
>>>
>>>
>>> On 09.10.2014 21:22, Krzysztof Sobkowiak wrote:
>>>> Do you propose following branches?
>>>>
>>>>    * 5.3.x with Karaf 2.4.x and Camel 2.13.x
>>>>    * 5.4.x with Karaf 2.4.x and Camel 2.14.x
>>>>
>>>> We"ve also planed
>>>>
>>>>    * 5.2.x with Karaf 2.3.x and Camel 2.13.x
>>>>
>>>> Regards
>>>> Krzysztof
>>>>
>>>>
>>>> On 09.10.2014 21:09, Gert Vanthienen wrote:
>>>>> L.S.,
>>>>>
>>>>> I agree it's a bit of a pain to maintain yet another branch and we
>>>>> should be careful not to create branches for every single permutation
>>>>> of Karaf/Camel/CXF/... versions, but doing a ServiceMix 5.3.0 with
>>>>> Karaf 2.4.0 and Camel 2.13.x and then upgrade to Camel 2.14.0 in a
>>>>> next 5.3.x version, just sounds like a bit of a "hack" just to avoid
>>>>> creating another branch.
>>>>>
>>>>> If we already do the work to get Camel 2.13.x working with Karaf
>>>>> 2.4.0, why not keep that combination around in a separate branch so we
>>>>> can do a follow-up release if a critical issue or a security problem
>>>>> arises in either Karaf 2.4.x or Camel 2.13.x. If we don't want to, we
>>>>> don't have to do a 5.3.1 release off that branch, but I think it would
>>>>> be better if we would at least give ourselves the option.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Gert Vanthienen
>>>>>
>>>>>
>>>>> On Thu, Oct 9, 2014 at 5:02 PM, Krzysztof Sobkowiak
>>>>> <kr...@gmail.com> wrote:
>>>>>> Hi
>>>>>>
>>>>>> Do you have any idea how to solve this problem. As discussed in Irc we
>>>>>> have 2 possible solutions (both have pros and cons)
>>>>>>
>>>>>>    * we can create a new branch for distribution based on Karaf 2.4.x and
>>>>>>      Camel 2.13.x, but in this case we will have one mor branch to maintain
>>>>>>    * wen can do 5.3.0 with Karaf 2.4.0 and Camel 2.13.x as pre-release
>>>>>>      and next 5.3.1+ with Camel 2.14.x to let people smooth transition
>>>>>>      from Karaf 2.3.x and Camel 2.14.x
>>>>>>
>>>>>> Wdyt?
>>>>>>
>>>>>> Regards
>>>>>> Krzysztof
>>>>>>
>>>>>>
>>>>>>
>>>>>> -------- Original Message --------
>>>>>> Subject:        Re: Release Schedule and request for release update using
>>>>>> Karaf 2.4.0
>>>>>> Date:   Thu, 9 Oct 2014 14:30:20 +0200
>>>>>> From:   Michael Täschner <m....@gmail.com>
>>>>>> Reply-To:       users@servicemix.apache.org
>>>>>> To:     users@servicemix.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi Krzysztof,
>>>>>>
>>>>>> thanks for the release schedule overview. Do you see any chance for the
>>>>>> combination of Karaf 2.4.0 + Camel 2.13.2 because incrementing directly to
>>>>>> Camel 2.14.0 will have big impact on our customized container where I have
>>>>>> to verify that every CXF interceptor we provide with the container (service
>>>>>> monitoring, statistics) will have to be tested with the major CXF release
>>>>>> change to 3.0.2?
>>>>>>
>>>>>> If not, do you have any recommendation how I could easily exchange the
>>>>>> karaf version only based on my ServiceMix 5.1.x build ?
>>>>>>
>>>>>> I will of course also look into taking the plunge towards ServiceMix 5.3 as
>>>>>> well ...
>>>>>>
>>>>>> Cheers,
>>>>>> Michael
>>>>>>
>>>>>> 2014-10-07 18:51 GMT+02:00 Krzysztof Sobkowiak <kr...@gmail.com>:
>>>>>>
>>>>>>> Hi Michael
>>>>>>>
>>>>>>> I have created initial version of the roadmap page. You can find it
>>>>>>> here  http://servicemix.apache.org/community/releases-schedule.html
>>>>>>>
>>>>>>> Best regards
>>>>>>> Krzysztof
>>>>>>>
>>>>>>> On 22.09.2014 11:16, Michael Täschner wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I have two questions regarding the servicemix roadmap ?
>>>>>>>> - Is there a overview page with servicemix roadmap similar to karaf (
>>>>>>>> http://karaf.apache.org/index/community/releases-schedule.html) ?
>>>>>>>> - Do you see a chance to prepare a 5.2.0 release with upgrade to Karaf
>>>>>>>> 2.4.0 ? I am really looking forward to updating to servlet-api 3.0 which
>>>>>>> is
>>>>>>>> provided by pax-web 3.x (contained in Karaf 2.4.0) and used by various
>>>>>>>> camel components (camel:websocket, camel:cxf, etc.)
>>>>>>>>
>>>>>>>> Thanks and Regards,
>>>>>>>> Michael
>>>>>>>>
>
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [DISCUSS] ServiceMix 5.3..x plans

Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
So, if no veto I would cut 5.3.0 next.

Regards
Krzysztof

On 09.10.2014 22:02, Gert Vanthienen wrote:
> L.S.,
>
> Yeah, that would be my preference:
>  * a 5.2.x branch with Karaf 2.3.x and Camel 2.14.x
>  * a 5.3.x branch with Karaf 2.4.x and Camel 2.13.x
>  * a 5.4.x branch with Karaf 2.4.x and Camel 2.14.x
>
> I think we're considering to do those releases (with those
> combinations of Karaf/Camel) anyway, so the only question is whether
> or not we create a separate branch for the 5.3.x and 5.4.x releases.
> In my mind, it would make sense to have a separate branch for those
> two, even if we only do 5.3.0 release off the 5.3.x branch and then
> move straight to 5.4.0. Just my 2 cents though...
>
> Regards,
>
> Gert Vanthienen
>
>
> On Thu, Oct 9, 2014 at 9:24 PM, Krzysztof Sobkowiak
> <kr...@gmail.com> wrote:
>> My mistake:
>>
>>   * 5.2.x with Karaf 2.3.x and Camel 2.14.x
>>
>>
>> On 09.10.2014 21:22, Krzysztof Sobkowiak wrote:
>>> Do you propose following branches?
>>>
>>>   * 5.3.x with Karaf 2.4.x and Camel 2.13.x
>>>   * 5.4.x with Karaf 2.4.x and Camel 2.14.x
>>>
>>> We"ve also planed
>>>
>>>   * 5.2.x with Karaf 2.3.x and Camel 2.13.x
>>>
>>> Regards
>>> Krzysztof
>>>
>>>
>>> On 09.10.2014 21:09, Gert Vanthienen wrote:
>>>> L.S.,
>>>>
>>>> I agree it's a bit of a pain to maintain yet another branch and we
>>>> should be careful not to create branches for every single permutation
>>>> of Karaf/Camel/CXF/... versions, but doing a ServiceMix 5.3.0 with
>>>> Karaf 2.4.0 and Camel 2.13.x and then upgrade to Camel 2.14.0 in a
>>>> next 5.3.x version, just sounds like a bit of a "hack" just to avoid
>>>> creating another branch.
>>>>
>>>> If we already do the work to get Camel 2.13.x working with Karaf
>>>> 2.4.0, why not keep that combination around in a separate branch so we
>>>> can do a follow-up release if a critical issue or a security problem
>>>> arises in either Karaf 2.4.x or Camel 2.13.x. If we don't want to, we
>>>> don't have to do a 5.3.1 release off that branch, but I think it would
>>>> be better if we would at least give ourselves the option.
>>>>
>>>> Regards,
>>>>
>>>> Gert Vanthienen
>>>>
>>>>
>>>> On Thu, Oct 9, 2014 at 5:02 PM, Krzysztof Sobkowiak
>>>> <kr...@gmail.com> wrote:
>>>>> Hi
>>>>>
>>>>> Do you have any idea how to solve this problem. As discussed in Irc we
>>>>> have 2 possible solutions (both have pros and cons)
>>>>>
>>>>>   * we can create a new branch for distribution based on Karaf 2.4.x and
>>>>>     Camel 2.13.x, but in this case we will have one mor branch to maintain
>>>>>   * wen can do 5.3.0 with Karaf 2.4.0 and Camel 2.13.x as pre-release
>>>>>     and next 5.3.1+ with Camel 2.14.x to let people smooth transition
>>>>>     from Karaf 2.3.x and Camel 2.14.x
>>>>>
>>>>> Wdyt?
>>>>>
>>>>> Regards
>>>>> Krzysztof
>>>>>
>>>>>
>>>>>
>>>>> -------- Original Message --------
>>>>> Subject:        Re: Release Schedule and request for release update using
>>>>> Karaf 2.4.0
>>>>> Date:   Thu, 9 Oct 2014 14:30:20 +0200
>>>>> From:   Michael Täschner <m....@gmail.com>
>>>>> Reply-To:       users@servicemix.apache.org
>>>>> To:     users@servicemix.apache.org
>>>>>
>>>>>
>>>>>
>>>>> Hi Krzysztof,
>>>>>
>>>>> thanks for the release schedule overview. Do you see any chance for the
>>>>> combination of Karaf 2.4.0 + Camel 2.13.2 because incrementing directly to
>>>>> Camel 2.14.0 will have big impact on our customized container where I have
>>>>> to verify that every CXF interceptor we provide with the container (service
>>>>> monitoring, statistics) will have to be tested with the major CXF release
>>>>> change to 3.0.2?
>>>>>
>>>>> If not, do you have any recommendation how I could easily exchange the
>>>>> karaf version only based on my ServiceMix 5.1.x build ?
>>>>>
>>>>> I will of course also look into taking the plunge towards ServiceMix 5.3 as
>>>>> well ...
>>>>>
>>>>> Cheers,
>>>>> Michael
>>>>>
>>>>> 2014-10-07 18:51 GMT+02:00 Krzysztof Sobkowiak <kr...@gmail.com>:
>>>>>
>>>>>> Hi Michael
>>>>>>
>>>>>> I have created initial version of the roadmap page. You can find it
>>>>>> here  http://servicemix.apache.org/community/releases-schedule.html
>>>>>>
>>>>>> Best regards
>>>>>> Krzysztof
>>>>>>
>>>>>> On 22.09.2014 11:16, Michael Täschner wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have two questions regarding the servicemix roadmap ?
>>>>>>> - Is there a overview page with servicemix roadmap similar to karaf (
>>>>>>> http://karaf.apache.org/index/community/releases-schedule.html) ?
>>>>>>> - Do you see a chance to prepare a 5.2.0 release with upgrade to Karaf
>>>>>>> 2.4.0 ? I am really looking forward to updating to servlet-api 3.0 which
>>>>>> is
>>>>>>> provided by pax-web 3.x (contained in Karaf 2.4.0) and used by various
>>>>>>> camel components (camel:websocket, camel:cxf, etc.)
>>>>>>>
>>>>>>> Thanks and Regards,
>>>>>>> Michael
>>>>>>>


-- 
Krzysztof Sobkowiak

JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC

Re: [DISCUSS] ServiceMix 5.3..x plans

Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,

Yeah, that would be my preference:
 * a 5.2.x branch with Karaf 2.3.x and Camel 2.14.x
 * a 5.3.x branch with Karaf 2.4.x and Camel 2.13.x
 * a 5.4.x branch with Karaf 2.4.x and Camel 2.14.x

I think we're considering to do those releases (with those
combinations of Karaf/Camel) anyway, so the only question is whether
or not we create a separate branch for the 5.3.x and 5.4.x releases.
In my mind, it would make sense to have a separate branch for those
two, even if we only do 5.3.0 release off the 5.3.x branch and then
move straight to 5.4.0. Just my 2 cents though...

Regards,

Gert Vanthienen


On Thu, Oct 9, 2014 at 9:24 PM, Krzysztof Sobkowiak
<kr...@gmail.com> wrote:
> My mistake:
>
>   * 5.2.x with Karaf 2.3.x and Camel 2.14.x
>
>
> On 09.10.2014 21:22, Krzysztof Sobkowiak wrote:
>>
>> Do you propose following branches?
>>
>>   * 5.3.x with Karaf 2.4.x and Camel 2.13.x
>>   * 5.4.x with Karaf 2.4.x and Camel 2.14.x
>>
>> We"ve also planed
>>
>>   * 5.2.x with Karaf 2.3.x and Camel 2.13.x
>>
>> Regards
>> Krzysztof
>>
>>
>> On 09.10.2014 21:09, Gert Vanthienen wrote:
>>> L.S.,
>>>
>>> I agree it's a bit of a pain to maintain yet another branch and we
>>> should be careful not to create branches for every single permutation
>>> of Karaf/Camel/CXF/... versions, but doing a ServiceMix 5.3.0 with
>>> Karaf 2.4.0 and Camel 2.13.x and then upgrade to Camel 2.14.0 in a
>>> next 5.3.x version, just sounds like a bit of a "hack" just to avoid
>>> creating another branch.
>>>
>>> If we already do the work to get Camel 2.13.x working with Karaf
>>> 2.4.0, why not keep that combination around in a separate branch so we
>>> can do a follow-up release if a critical issue or a security problem
>>> arises in either Karaf 2.4.x or Camel 2.13.x. If we don't want to, we
>>> don't have to do a 5.3.1 release off that branch, but I think it would
>>> be better if we would at least give ourselves the option.
>>>
>>> Regards,
>>>
>>> Gert Vanthienen
>>>
>>>
>>> On Thu, Oct 9, 2014 at 5:02 PM, Krzysztof Sobkowiak
>>> <kr...@gmail.com> wrote:
>>>> Hi
>>>>
>>>> Do you have any idea how to solve this problem. As discussed in Irc we
>>>> have 2 possible solutions (both have pros and cons)
>>>>
>>>>   * we can create a new branch for distribution based on Karaf 2.4.x and
>>>>     Camel 2.13.x, but in this case we will have one mor branch to maintain
>>>>   * wen can do 5.3.0 with Karaf 2.4.0 and Camel 2.13.x as pre-release
>>>>     and next 5.3.1+ with Camel 2.14.x to let people smooth transition
>>>>     from Karaf 2.3.x and Camel 2.14.x
>>>>
>>>> Wdyt?
>>>>
>>>> Regards
>>>> Krzysztof
>>>>
>>>>
>>>>
>>>> -------- Original Message --------
>>>> Subject:        Re: Release Schedule and request for release update using
>>>> Karaf 2.4.0
>>>> Date:   Thu, 9 Oct 2014 14:30:20 +0200
>>>> From:   Michael Täschner <m....@gmail.com>
>>>> Reply-To:       users@servicemix.apache.org
>>>> To:     users@servicemix.apache.org
>>>>
>>>>
>>>>
>>>> Hi Krzysztof,
>>>>
>>>> thanks for the release schedule overview. Do you see any chance for the
>>>> combination of Karaf 2.4.0 + Camel 2.13.2 because incrementing directly to
>>>> Camel 2.14.0 will have big impact on our customized container where I have
>>>> to verify that every CXF interceptor we provide with the container (service
>>>> monitoring, statistics) will have to be tested with the major CXF release
>>>> change to 3.0.2?
>>>>
>>>> If not, do you have any recommendation how I could easily exchange the
>>>> karaf version only based on my ServiceMix 5.1.x build ?
>>>>
>>>> I will of course also look into taking the plunge towards ServiceMix 5.3 as
>>>> well ...
>>>>
>>>> Cheers,
>>>> Michael
>>>>
>>>> 2014-10-07 18:51 GMT+02:00 Krzysztof Sobkowiak <kr...@gmail.com>:
>>>>
>>>>> Hi Michael
>>>>>
>>>>> I have created initial version of the roadmap page. You can find it
>>>>> here  http://servicemix.apache.org/community/releases-schedule.html
>>>>>
>>>>> Best regards
>>>>> Krzysztof
>>>>>
>>>>> On 22.09.2014 11:16, Michael Täschner wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I have two questions regarding the servicemix roadmap ?
>>>>>> - Is there a overview page with servicemix roadmap similar to karaf (
>>>>>> http://karaf.apache.org/index/community/releases-schedule.html) ?
>>>>>> - Do you see a chance to prepare a 5.2.0 release with upgrade to Karaf
>>>>>> 2.4.0 ? I am really looking forward to updating to servlet-api 3.0 which
>>>>> is
>>>>>> provided by pax-web 3.x (contained in Karaf 2.4.0) and used by various
>>>>>> camel components (camel:websocket, camel:cxf, etc.)
>>>>>>
>>>>>> Thanks and Regards,
>>>>>> Michael
>>>>>>
>>>>>
>>
>> --
>> Krzysztof Sobkowiak
>>
>> JEE & OSS Architect | Senior Solution Architect @ Capgemini |
>> Committer @ ASF
>> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
>> <http://www.pl.capgemini-sdm.com/> | Wroclaw
>> e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
>> Twitter: @KSobkowiak
>> Calendar: http://goo.gl/yvsebC
>
>
> --
> Krzysztof Sobkowiak
>
> JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
> @ ASF
> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
> <http://www.pl.capgemini-sdm.com/> | Wroclaw
> e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
> Twitter: @KSobkowiak
> Calendar: http://goo.gl/yvsebC

Re: [DISCUSS] ServiceMix 5.3..x plans

Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
My mistake:

  * 5.2.x with Karaf 2.3.x and Camel 2.14.x


On 09.10.2014 21:22, Krzysztof Sobkowiak wrote:
>
> Do you propose following branches?
>
>   * 5.3.x with Karaf 2.4.x and Camel 2.13.x
>   * 5.4.x with Karaf 2.4.x and Camel 2.14.x
>
> We"ve also planed
>
>   * 5.2.x with Karaf 2.3.x and Camel 2.13.x
>
> Regards
> Krzysztof
>
>
> On 09.10.2014 21:09, Gert Vanthienen wrote:
>> L.S.,
>>
>> I agree it's a bit of a pain to maintain yet another branch and we
>> should be careful not to create branches for every single permutation
>> of Karaf/Camel/CXF/... versions, but doing a ServiceMix 5.3.0 with
>> Karaf 2.4.0 and Camel 2.13.x and then upgrade to Camel 2.14.0 in a
>> next 5.3.x version, just sounds like a bit of a "hack" just to avoid
>> creating another branch.
>>
>> If we already do the work to get Camel 2.13.x working with Karaf
>> 2.4.0, why not keep that combination around in a separate branch so we
>> can do a follow-up release if a critical issue or a security problem
>> arises in either Karaf 2.4.x or Camel 2.13.x. If we don't want to, we
>> don't have to do a 5.3.1 release off that branch, but I think it would
>> be better if we would at least give ourselves the option.
>>
>> Regards,
>>
>> Gert Vanthienen
>>
>>
>> On Thu, Oct 9, 2014 at 5:02 PM, Krzysztof Sobkowiak
>> <kr...@gmail.com> wrote:
>>> Hi
>>>
>>> Do you have any idea how to solve this problem. As discussed in Irc we
>>> have 2 possible solutions (both have pros and cons)
>>>
>>>   * we can create a new branch for distribution based on Karaf 2.4.x and
>>>     Camel 2.13.x, but in this case we will have one mor branch to maintain
>>>   * wen can do 5.3.0 with Karaf 2.4.0 and Camel 2.13.x as pre-release
>>>     and next 5.3.1+ with Camel 2.14.x to let people smooth transition
>>>     from Karaf 2.3.x and Camel 2.14.x
>>>
>>> Wdyt?
>>>
>>> Regards
>>> Krzysztof
>>>
>>>
>>>
>>> -------- Original Message --------
>>> Subject:        Re: Release Schedule and request for release update using
>>> Karaf 2.4.0
>>> Date:   Thu, 9 Oct 2014 14:30:20 +0200
>>> From:   Michael Täschner <m....@gmail.com>
>>> Reply-To:       users@servicemix.apache.org
>>> To:     users@servicemix.apache.org
>>>
>>>
>>>
>>> Hi Krzysztof,
>>>
>>> thanks for the release schedule overview. Do you see any chance for the
>>> combination of Karaf 2.4.0 + Camel 2.13.2 because incrementing directly to
>>> Camel 2.14.0 will have big impact on our customized container where I have
>>> to verify that every CXF interceptor we provide with the container (service
>>> monitoring, statistics) will have to be tested with the major CXF release
>>> change to 3.0.2?
>>>
>>> If not, do you have any recommendation how I could easily exchange the
>>> karaf version only based on my ServiceMix 5.1.x build ?
>>>
>>> I will of course also look into taking the plunge towards ServiceMix 5.3 as
>>> well ...
>>>
>>> Cheers,
>>> Michael
>>>
>>> 2014-10-07 18:51 GMT+02:00 Krzysztof Sobkowiak <kr...@gmail.com>:
>>>
>>>> Hi Michael
>>>>
>>>> I have created initial version of the roadmap page. You can find it
>>>> here  http://servicemix.apache.org/community/releases-schedule.html
>>>>
>>>> Best regards
>>>> Krzysztof
>>>>
>>>> On 22.09.2014 11:16, Michael Täschner wrote:
>>>>> Hi,
>>>>>
>>>>> I have two questions regarding the servicemix roadmap ?
>>>>> - Is there a overview page with servicemix roadmap similar to karaf (
>>>>> http://karaf.apache.org/index/community/releases-schedule.html) ?
>>>>> - Do you see a chance to prepare a 5.2.0 release with upgrade to Karaf
>>>>> 2.4.0 ? I am really looking forward to updating to servlet-api 3.0 which
>>>> is
>>>>> provided by pax-web 3.x (contained in Karaf 2.4.0) and used by various
>>>>> camel components (camel:websocket, camel:cxf, etc.)
>>>>>
>>>>> Thanks and Regards,
>>>>> Michael
>>>>>
>>>>
>
> -- 
> Krzysztof Sobkowiak
>
> JEE & OSS Architect | Senior Solution Architect @ Capgemini |
> Committer @ ASF
> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
> <http://www.pl.capgemini-sdm.com/> | Wroclaw
> e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
> Twitter: @KSobkowiak
> Calendar: http://goo.gl/yvsebC


-- 
Krzysztof Sobkowiak

JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC

Re: [DISCUSS] ServiceMix 5.3..x plans

Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
Do you propose following branches?

  * 5.3.x with Karaf 2.4.x and Camel 2.13.x
  * 5.4.x with Karaf 2.4.x and Camel 2.14.x

We"ve also planed

  * 5.2.x with Karaf 2.3.x and Camel 2.13.x

Regards
Krzysztof


On 09.10.2014 21:09, Gert Vanthienen wrote:
> L.S.,
>
> I agree it's a bit of a pain to maintain yet another branch and we
> should be careful not to create branches for every single permutation
> of Karaf/Camel/CXF/... versions, but doing a ServiceMix 5.3.0 with
> Karaf 2.4.0 and Camel 2.13.x and then upgrade to Camel 2.14.0 in a
> next 5.3.x version, just sounds like a bit of a "hack" just to avoid
> creating another branch.
>
> If we already do the work to get Camel 2.13.x working with Karaf
> 2.4.0, why not keep that combination around in a separate branch so we
> can do a follow-up release if a critical issue or a security problem
> arises in either Karaf 2.4.x or Camel 2.13.x. If we don't want to, we
> don't have to do a 5.3.1 release off that branch, but I think it would
> be better if we would at least give ourselves the option.
>
> Regards,
>
> Gert Vanthienen
>
>
> On Thu, Oct 9, 2014 at 5:02 PM, Krzysztof Sobkowiak
> <kr...@gmail.com> wrote:
>> Hi
>>
>> Do you have any idea how to solve this problem. As discussed in Irc we
>> have 2 possible solutions (both have pros and cons)
>>
>>   * we can create a new branch for distribution based on Karaf 2.4.x and
>>     Camel 2.13.x, but in this case we will have one mor branch to maintain
>>   * wen can do 5.3.0 with Karaf 2.4.0 and Camel 2.13.x as pre-release
>>     and next 5.3.1+ with Camel 2.14.x to let people smooth transition
>>     from Karaf 2.3.x and Camel 2.14.x
>>
>> Wdyt?
>>
>> Regards
>> Krzysztof
>>
>>
>>
>> -------- Original Message --------
>> Subject:        Re: Release Schedule and request for release update using
>> Karaf 2.4.0
>> Date:   Thu, 9 Oct 2014 14:30:20 +0200
>> From:   Michael Täschner <m....@gmail.com>
>> Reply-To:       users@servicemix.apache.org
>> To:     users@servicemix.apache.org
>>
>>
>>
>> Hi Krzysztof,
>>
>> thanks for the release schedule overview. Do you see any chance for the
>> combination of Karaf 2.4.0 + Camel 2.13.2 because incrementing directly to
>> Camel 2.14.0 will have big impact on our customized container where I have
>> to verify that every CXF interceptor we provide with the container (service
>> monitoring, statistics) will have to be tested with the major CXF release
>> change to 3.0.2?
>>
>> If not, do you have any recommendation how I could easily exchange the
>> karaf version only based on my ServiceMix 5.1.x build ?
>>
>> I will of course also look into taking the plunge towards ServiceMix 5.3 as
>> well ...
>>
>> Cheers,
>> Michael
>>
>> 2014-10-07 18:51 GMT+02:00 Krzysztof Sobkowiak <kr...@gmail.com>:
>>
>>> Hi Michael
>>>
>>> I have created initial version of the roadmap page. You can find it
>>> here  http://servicemix.apache.org/community/releases-schedule.html
>>>
>>> Best regards
>>> Krzysztof
>>>
>>> On 22.09.2014 11:16, Michael Täschner wrote:
>>>> Hi,
>>>>
>>>> I have two questions regarding the servicemix roadmap ?
>>>> - Is there a overview page with servicemix roadmap similar to karaf (
>>>> http://karaf.apache.org/index/community/releases-schedule.html) ?
>>>> - Do you see a chance to prepare a 5.2.0 release with upgrade to Karaf
>>>> 2.4.0 ? I am really looking forward to updating to servlet-api 3.0 which
>>> is
>>>> provided by pax-web 3.x (contained in Karaf 2.4.0) and used by various
>>>> camel components (camel:websocket, camel:cxf, etc.)
>>>>
>>>> Thanks and Regards,
>>>> Michael
>>>>
>>>

-- 
Krzysztof Sobkowiak

JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC

Re: [DISCUSS] ServiceMix 5.3..x plans (was: Re: Release Schedule and request for release update using Karaf 2.4.0)

Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,

I agree it's a bit of a pain to maintain yet another branch and we
should be careful not to create branches for every single permutation
of Karaf/Camel/CXF/... versions, but doing a ServiceMix 5.3.0 with
Karaf 2.4.0 and Camel 2.13.x and then upgrade to Camel 2.14.0 in a
next 5.3.x version, just sounds like a bit of a "hack" just to avoid
creating another branch.

If we already do the work to get Camel 2.13.x working with Karaf
2.4.0, why not keep that combination around in a separate branch so we
can do a follow-up release if a critical issue or a security problem
arises in either Karaf 2.4.x or Camel 2.13.x. If we don't want to, we
don't have to do a 5.3.1 release off that branch, but I think it would
be better if we would at least give ourselves the option.

Regards,

Gert Vanthienen


On Thu, Oct 9, 2014 at 5:02 PM, Krzysztof Sobkowiak
<kr...@gmail.com> wrote:
> Hi
>
> Do you have any idea how to solve this problem. As discussed in Irc we
> have 2 possible solutions (both have pros and cons)
>
>   * we can create a new branch for distribution based on Karaf 2.4.x and
>     Camel 2.13.x, but in this case we will have one mor branch to maintain
>   * wen can do 5.3.0 with Karaf 2.4.0 and Camel 2.13.x as pre-release
>     and next 5.3.1+ with Camel 2.14.x to let people smooth transition
>     from Karaf 2.3.x and Camel 2.14.x
>
> Wdyt?
>
> Regards
> Krzysztof
>
>
>
> -------- Original Message --------
> Subject:        Re: Release Schedule and request for release update using
> Karaf 2.4.0
> Date:   Thu, 9 Oct 2014 14:30:20 +0200
> From:   Michael Täschner <m....@gmail.com>
> Reply-To:       users@servicemix.apache.org
> To:     users@servicemix.apache.org
>
>
>
> Hi Krzysztof,
>
> thanks for the release schedule overview. Do you see any chance for the
> combination of Karaf 2.4.0 + Camel 2.13.2 because incrementing directly to
> Camel 2.14.0 will have big impact on our customized container where I have
> to verify that every CXF interceptor we provide with the container (service
> monitoring, statistics) will have to be tested with the major CXF release
> change to 3.0.2?
>
> If not, do you have any recommendation how I could easily exchange the
> karaf version only based on my ServiceMix 5.1.x build ?
>
> I will of course also look into taking the plunge towards ServiceMix 5.3 as
> well ...
>
> Cheers,
> Michael
>
> 2014-10-07 18:51 GMT+02:00 Krzysztof Sobkowiak <kr...@gmail.com>:
>
>> Hi Michael
>>
>> I have created initial version of the roadmap page. You can find it
>> here  http://servicemix.apache.org/community/releases-schedule.html
>>
>> Best regards
>> Krzysztof
>>
>> On 22.09.2014 11:16, Michael Täschner wrote:
>> > Hi,
>> >
>> > I have two questions regarding the servicemix roadmap ?
>> > - Is there a overview page with servicemix roadmap similar to karaf (
>> > http://karaf.apache.org/index/community/releases-schedule.html) ?
>> > - Do you see a chance to prepare a 5.2.0 release with upgrade to Karaf
>> > 2.4.0 ? I am really looking forward to updating to servlet-api 3.0 which
>> is
>> > provided by pax-web 3.x (contained in Karaf 2.4.0) and used by various
>> > camel components (camel:websocket, camel:cxf, etc.)
>> >
>> > Thanks and Regards,
>> > Michael
>> >
>>
>>
>> --
>> Krzysztof Sobkowiak
>>
>> JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
>> @ ASF
>> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
>> <http://www.pl.capgemini-sdm.com/> | Wroclaw
>> e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
>> Twitter: @KSobkowiak
>> Calendar: http://goo.gl/yvsebC
>>
>
>
>

Re: [DISCUSS] ServiceMix 5.3..x plans

Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
For me is 2nd option better too. But the community must be informed this
is the only version with this configuration and next version will be
upgraded to Camel 2.14.x. The should use 5.3.0 only for migration to
final 5.3.x version.

Regards
Krzysztof

On 09.10.2014 17:23, Achim Nierbeck wrote:
> I'd go for solution 2 also ...
>
> regards, Achim
>
> 2014-10-09 17:09 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
>
>> Hi Krzysztof,
>>
>> I would go for point 2.
>>
>> My $0.02
>>
>> Regards
>> JB
>>
>> On 10/09/2014 05:02 PM, Krzysztof Sobkowiak wrote:
>>
>>> Hi
>>>
>>> Do you have any idea how to solve this problem. As discussed in Irc we
>>> have 2 possible solutions (both have pros and cons)
>>>
>>>    * we can create a new branch for distribution based on Karaf 2.4.x and
>>>      Camel 2.13.x, but in this case we will have one mor branch to
>>> maintain
>>>    * wen can do 5.3.0 with Karaf 2.4.0 and Camel 2.13.x as pre-release
>>>      and next 5.3.1+ with Camel 2.14.x to let people smooth transition
>>>      from Karaf 2.3.x and Camel 2.14.x
>>>
>>> Wdyt?
>>>
>>> Regards
>>> Krzysztof
>>>
>>>
>>>
>>> -------- Original Message --------
>>> Subject:        Re: Release Schedule and request for release update using
>>> Karaf 2.4.0
>>> Date:   Thu, 9 Oct 2014 14:30:20 +0200
>>> From:   Michael Täschner <m....@gmail.com>
>>> Reply-To:       users@servicemix.apache.org
>>> To:     users@servicemix.apache.org
>>>
>>>
>>>
>>> Hi Krzysztof,
>>>
>>> thanks for the release schedule overview. Do you see any chance for the
>>> combination of Karaf 2.4.0 + Camel 2.13.2 because incrementing directly to
>>> Camel 2.14.0 will have big impact on our customized container where I have
>>> to verify that every CXF interceptor we provide with the container
>>> (service
>>> monitoring, statistics) will have to be tested with the major CXF release
>>> change to 3.0.2?
>>>
>>> If not, do you have any recommendation how I could easily exchange the
>>> karaf version only based on my ServiceMix 5.1.x build ?
>>>
>>> I will of course also look into taking the plunge towards ServiceMix 5.3
>>> as
>>> well ...
>>>
>>> Cheers,
>>> Michael
>>>
>>> 2014-10-07 18:51 GMT+02:00 Krzysztof Sobkowiak <krzys.sobkowiak@gmail.com
>>>> :
>>>  Hi Michael
>>>> I have created initial version of the roadmap page. You can find it
>>>> here  http://servicemix.apache.org/community/releases-schedule.html
>>>>
>>>> Best regards
>>>> Krzysztof
>>>>
>>>> On 22.09.2014 11:16, Michael Täschner wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have two questions regarding the servicemix roadmap ?
>>>>> - Is there a overview page with servicemix roadmap similar to karaf (
>>>>> http://karaf.apache.org/index/community/releases-schedule.html) ?
>>>>> - Do you see a chance to prepare a 5.2.0 release with upgrade to Karaf
>>>>> 2.4.0 ? I am really looking forward to updating to servlet-api 3.0 which
>>>>>
>>>> is
>>>>
>>>>> provided by pax-web 3.x (contained in Karaf 2.4.0) and used by various
>>>>> camel components (camel:websocket, camel:cxf, etc.)
>>>>>
>>>>> Thanks and Regards,
>>>>> Michael
>>>>>
>>>>>
>>>> --
>>>> Krzysztof Sobkowiak
>>>>
>>>> JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
>>>> @ ASF
>>>> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
>>>> <http://www.pl.capgemini-sdm.com/> | Wroclaw
>>>> e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
>>>> Twitter: @KSobkowiak
>>>> Calendar: http://goo.gl/yvsebC
>>>>
>>>>
>>>
>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>


-- 
Krzysztof Sobkowiak

JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC

Re: [DISCUSS] ServiceMix 5.3..x plans

Posted by Achim Nierbeck <bc...@googlemail.com>.
I'd go for solution 2 also ...

regards, Achim

2014-10-09 17:09 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:

> Hi Krzysztof,
>
> I would go for point 2.
>
> My $0.02
>
> Regards
> JB
>
> On 10/09/2014 05:02 PM, Krzysztof Sobkowiak wrote:
>
>> Hi
>>
>> Do you have any idea how to solve this problem. As discussed in Irc we
>> have 2 possible solutions (both have pros and cons)
>>
>>    * we can create a new branch for distribution based on Karaf 2.4.x and
>>      Camel 2.13.x, but in this case we will have one mor branch to
>> maintain
>>    * wen can do 5.3.0 with Karaf 2.4.0 and Camel 2.13.x as pre-release
>>      and next 5.3.1+ with Camel 2.14.x to let people smooth transition
>>      from Karaf 2.3.x and Camel 2.14.x
>>
>> Wdyt?
>>
>> Regards
>> Krzysztof
>>
>>
>>
>> -------- Original Message --------
>> Subject:        Re: Release Schedule and request for release update using
>> Karaf 2.4.0
>> Date:   Thu, 9 Oct 2014 14:30:20 +0200
>> From:   Michael Täschner <m....@gmail.com>
>> Reply-To:       users@servicemix.apache.org
>> To:     users@servicemix.apache.org
>>
>>
>>
>> Hi Krzysztof,
>>
>> thanks for the release schedule overview. Do you see any chance for the
>> combination of Karaf 2.4.0 + Camel 2.13.2 because incrementing directly to
>> Camel 2.14.0 will have big impact on our customized container where I have
>> to verify that every CXF interceptor we provide with the container
>> (service
>> monitoring, statistics) will have to be tested with the major CXF release
>> change to 3.0.2?
>>
>> If not, do you have any recommendation how I could easily exchange the
>> karaf version only based on my ServiceMix 5.1.x build ?
>>
>> I will of course also look into taking the plunge towards ServiceMix 5.3
>> as
>> well ...
>>
>> Cheers,
>> Michael
>>
>> 2014-10-07 18:51 GMT+02:00 Krzysztof Sobkowiak <krzys.sobkowiak@gmail.com
>> >:
>>
>>  Hi Michael
>>>
>>> I have created initial version of the roadmap page. You can find it
>>> here  http://servicemix.apache.org/community/releases-schedule.html
>>>
>>> Best regards
>>> Krzysztof
>>>
>>> On 22.09.2014 11:16, Michael Täschner wrote:
>>>
>>>> Hi,
>>>>
>>>> I have two questions regarding the servicemix roadmap ?
>>>> - Is there a overview page with servicemix roadmap similar to karaf (
>>>> http://karaf.apache.org/index/community/releases-schedule.html) ?
>>>> - Do you see a chance to prepare a 5.2.0 release with upgrade to Karaf
>>>> 2.4.0 ? I am really looking forward to updating to servlet-api 3.0 which
>>>>
>>> is
>>>
>>>> provided by pax-web 3.x (contained in Karaf 2.4.0) and used by various
>>>> camel components (camel:websocket, camel:cxf, etc.)
>>>>
>>>> Thanks and Regards,
>>>> Michael
>>>>
>>>>
>>>
>>> --
>>> Krzysztof Sobkowiak
>>>
>>> JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
>>> @ ASF
>>> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
>>> <http://www.pl.capgemini-sdm.com/> | Wroclaw
>>> e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
>>> Twitter: @KSobkowiak
>>> Calendar: http://goo.gl/yvsebC
>>>
>>>
>>
>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>



-- 

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>

Software Architect / Project Manager / Scrum Master

Re: [DISCUSS] ServiceMix 5.3..x plans

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Krzysztof,

I would go for point 2.

My $0.02

Regards
JB

On 10/09/2014 05:02 PM, Krzysztof Sobkowiak wrote:
> Hi
>
> Do you have any idea how to solve this problem. As discussed in Irc we
> have 2 possible solutions (both have pros and cons)
>
>    * we can create a new branch for distribution based on Karaf 2.4.x and
>      Camel 2.13.x, but in this case we will have one mor branch to maintain
>    * wen can do 5.3.0 with Karaf 2.4.0 and Camel 2.13.x as pre-release
>      and next 5.3.1+ with Camel 2.14.x to let people smooth transition
>      from Karaf 2.3.x and Camel 2.14.x
>
> Wdyt?
>
> Regards
> Krzysztof
>
>
>
> -------- Original Message --------
> Subject: 	Re: Release Schedule and request for release update using
> Karaf 2.4.0
> Date: 	Thu, 9 Oct 2014 14:30:20 +0200
> From: 	Michael Täschner <m....@gmail.com>
> Reply-To: 	users@servicemix.apache.org
> To: 	users@servicemix.apache.org
>
>
>
> Hi Krzysztof,
>
> thanks for the release schedule overview. Do you see any chance for the
> combination of Karaf 2.4.0 + Camel 2.13.2 because incrementing directly to
> Camel 2.14.0 will have big impact on our customized container where I have
> to verify that every CXF interceptor we provide with the container (service
> monitoring, statistics) will have to be tested with the major CXF release
> change to 3.0.2?
>
> If not, do you have any recommendation how I could easily exchange the
> karaf version only based on my ServiceMix 5.1.x build ?
>
> I will of course also look into taking the plunge towards ServiceMix 5.3 as
> well ...
>
> Cheers,
> Michael
>
> 2014-10-07 18:51 GMT+02:00 Krzysztof Sobkowiak <kr...@gmail.com>:
>
>> Hi Michael
>>
>> I have created initial version of the roadmap page. You can find it
>> here  http://servicemix.apache.org/community/releases-schedule.html
>>
>> Best regards
>> Krzysztof
>>
>> On 22.09.2014 11:16, Michael Täschner wrote:
>>> Hi,
>>>
>>> I have two questions regarding the servicemix roadmap ?
>>> - Is there a overview page with servicemix roadmap similar to karaf (
>>> http://karaf.apache.org/index/community/releases-schedule.html) ?
>>> - Do you see a chance to prepare a 5.2.0 release with upgrade to Karaf
>>> 2.4.0 ? I am really looking forward to updating to servlet-api 3.0 which
>> is
>>> provided by pax-web 3.x (contained in Karaf 2.4.0) and used by various
>>> camel components (camel:websocket, camel:cxf, etc.)
>>>
>>> Thanks and Regards,
>>> Michael
>>>
>>
>>
>> --
>> Krzysztof Sobkowiak
>>
>> JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
>> @ ASF
>> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
>> <http://www.pl.capgemini-sdm.com/> | Wroclaw
>> e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
>> Twitter: @KSobkowiak
>> Calendar: http://goo.gl/yvsebC
>>
>
>
>
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [DISCUSS] ServiceMix 5.3..x plans

Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
Hi

ServiceMix 5.3.x will be shipped with Karaf 2.4.x and Camel 2.14.x. We
will probably release 5.3.0 with Karaf 2.4.0 and Camel 2.13.x as
pre-release and next 5.3.1 upgraded to Camel 2.14.x

Regards
Krzysztof

On 09.10.2014 18:18, Ge@@ru wrote:
> Hi,
>
> i'm currently wait for an important issue on use cellar with smx (at 
> least for me) to manage osgi service in cluster and so, to avoid more 
> of one refactory of all my bundles i think that could be valid a third 
> solution with:
>
> * karaf-2.4.x
> * camel-2.14.x
>
> But if this is too complicated probably solution 2.
>
> My cent.
>
> Regards
>
> On Thu, 2014-10-09 at 17:02 +0200, Krzysztof Sobkowiak wrote:
>> Hi
>>
>> Do you have any idea how to solve this problem. As discussed in Irc 
>> we
>> have 2 possible solutions (both have pros and cons)
>>
>>   * we can create a new branch for distribution based on Karaf 2.4.x 
>> and
>>     Camel 2.13.x, but in this case we will have one mor branch to 
>> maintain
>>   * wen can do 5.3.0 with Karaf 2.4.0 and Camel 2.13.x as pre-release
>>     and next 5.3.1+ with Camel 2.14.x to let people smooth transition
>>     from Karaf 2.3.x and Camel 2.14.x
>>
>> Wdyt?
>>
>> Regards
>> Krzysztof
>>
>>
>>
>> -------- Original Message --------
>> Subject:        Re: Release Schedule and request for release update 
>> using
>> Karaf 2.4.0
>> Date:   Thu, 9 Oct 2014 14:30:20 +0200
>> From:   Michael Täschner taeschner@gmail.com>
>> Reply-To:       users@servicemix.apache.org
>> To:     users@servicemix.apache.org
>>
>>
>>
>> Hi Krzysztof,
>>
>> thanks for the release schedule overview. Do you see any chance for 
>> the
>> combination of Karaf 2.4.0 + Camel 2.13.2 because incrementing 
>> directly to
>> Camel 2.14.0 will have big impact on our customized container where I
>> have
>> to verify that every CXF interceptor we provide with the container 
>> (service
>> monitoring, statistics) will have to be tested with the major CXF 
>> release
>> change to 3.0.2?
>>
>> If not, do you have any recommendation how I could easily exchange 
>> the
>> karaf version only based on my ServiceMix 5.1.x build ?
>>
>> I will of course also look into taking the plunge towards ServiceMix 
>> 5.3 as
>> well ...
>>
>> Cheers,
>> Michael
>>
>> 2014-10-07 18:51 GMT+02:00 Krzysztof Sobkowiak 
>> sobkowiak@gmail.com>:
>>
>>>  Hi Michael
>>>  I have created initial version of the roadmap page. You can find 
>>> it
>>>  here  
>>> http://servicemix.apache.org/community/releases-schedule.html
>>>  Best regards
>>>  Krzysztof
>>>  On 22.09.2014 11:16, Michael Täschner wrote:
>>>>  Hi,
>>>>  I have two questions regarding the servicemix roadmap ?
>>>>  - Is there a overview page with servicemix roadmap similar to 
>>>> karaf (
>>>>  http://karaf.apache.org/index/community/releases-schedule.html) 
>>>> ?
>>>>  - Do you see a chance to prepare a 5.2.0 release with upgrade 
>>>> to Karaf
>>>>  2.4.0 ? I am really looking forward to updating to servlet-api 
>>>> 3.0 which
>>>  is
>>>>  provided by pax-web 3.x (contained in Karaf 2.4.0) and used by 
>>>> various
>>>>  camel components (camel:websocket, camel:cxf, etc.)
>>>>  Thanks and Regards,
>>>>  Michael
>>>>
>>>  --
>>>  Krzysztof Sobkowiak
>>>  JEE & OSS Architect | Senior Solution Architect @ Capgemini | 
>>> Committer
>>>  @ ASF
>>>  Capgemini <http://www.pl.capgemini.com/> | Software Solutions 
>>> Center
>>>  <http://www.pl.capgemini-sdm.com/> | Wroclaw
>>>  e-mail: krzys.sobkowiak@gmail.com <
>>> mailto:krzys.sobkowiak@gmail.com> |
>>>  Twitter: @KSobkowiak
>>>  Calendar: http://goo.gl/yvsebC
>>
>>
>>


-- 
Krzysztof Sobkowiak

JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC

Re: [DISCUSS] ServiceMix 5.3..x plans (was: Re: Release Schedule and request for release update using Karaf 2.4.0)

Posted by "Ge@@ru" <ge...@gmail.com>.
Hi,

i'm currently wait for an important issue on use cellar with smx (at 
least for me) to manage osgi service in cluster and so, to avoid more 
of one refactory of all my bundles i think that could be valid a third 
solution with:

* karaf-2.4.x
* camel-2.14.x

But if this is too complicated probably solution 2.

My cent.

Regards

On Thu, 2014-10-09 at 17:02 +0200, Krzysztof Sobkowiak wrote:
> Hi
> 
> Do you have any idea how to solve this problem. As discussed in Irc 
> we
> have 2 possible solutions (both have pros and cons)
> 
>   * we can create a new branch for distribution based on Karaf 2.4.x 
> and
>     Camel 2.13.x, but in this case we will have one mor branch to 
> maintain
>   * wen can do 5.3.0 with Karaf 2.4.0 and Camel 2.13.x as pre-release
>     and next 5.3.1+ with Camel 2.14.x to let people smooth transition
>     from Karaf 2.3.x and Camel 2.14.x
> 
> Wdyt?
> 
> Regards
> Krzysztof
> 
> 
> 
> -------- Original Message --------
> Subject:        Re: Release Schedule and request for release update 
> using
> Karaf 2.4.0
> Date:   Thu, 9 Oct 2014 14:30:20 +0200
> From:   Michael Täschner taeschner@gmail.com>
> Reply-To:       users@servicemix.apache.org
> To:     users@servicemix.apache.org
> 
> 
> 
> Hi Krzysztof,
> 
> thanks for the release schedule overview. Do you see any chance for 
> the
> combination of Karaf 2.4.0 + Camel 2.13.2 because incrementing 
> directly to
> Camel 2.14.0 will have big impact on our customized container where I
> have
> to verify that every CXF interceptor we provide with the container 
> (service
> monitoring, statistics) will have to be tested with the major CXF 
> release
> change to 3.0.2?
> 
> If not, do you have any recommendation how I could easily exchange 
> the
> karaf version only based on my ServiceMix 5.1.x build ?
> 
> I will of course also look into taking the plunge towards ServiceMix 
> 5.3 as
> well ...
> 
> Cheers,
> Michael
> 
> 2014-10-07 18:51 GMT+02:00 Krzysztof Sobkowiak 
> sobkowiak@gmail.com>:
> 
> >  Hi Michael
> > >
> >  I have created initial version of the roadmap page. You can find 
> > it
> >  here  
> > http://servicemix.apache.org/community/releases-schedule.html
> > >
> >  Best regards
> >  Krzysztof
> > >
> >  On 22.09.2014 11:16, Michael Täschner wrote:
> > >  Hi,
> > > >
> > >  I have two questions regarding the servicemix roadmap ?
> > >  - Is there a overview page with servicemix roadmap similar to 
> > > karaf (
> > >  http://karaf.apache.org/index/community/releases-schedule.html) 
> > > ?
> > >  - Do you see a chance to prepare a 5.2.0 release with upgrade 
> > > to Karaf
> > >  2.4.0 ? I am really looking forward to updating to servlet-api 
> > > 3.0 which
> >  is
> > >  provided by pax-web 3.x (contained in Karaf 2.4.0) and used by 
> > > various
> > >  camel components (camel:websocket, camel:cxf, etc.)
> > > >
> > >  Thanks and Regards,
> > >  Michael
> > > >
> > >
> > >
> >  --
> >  Krzysztof Sobkowiak
> > >
> >  JEE & OSS Architect | Senior Solution Architect @ Capgemini | 
> > Committer
> >  @ ASF
> >  Capgemini <http://www.pl.capgemini.com/> | Software Solutions 
> > Center
> >  <http://www.pl.capgemini-sdm.com/> | Wroclaw
> >  e-mail: krzys.sobkowiak@gmail.com <
> > mailto:krzys.sobkowiak@gmail.com> |
> >  Twitter: @KSobkowiak
> >  Calendar: http://goo.gl/yvsebC
> > >
> 
> 
> 
>