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é <[email protected]>:
>
>> 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 <[email protected]>
>>> Reply-To:       [email protected]
>>> To:     [email protected]
>>>
>>>
>>>
>>> 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 <[email protected]
>>>> :
>>>  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: [email protected] <mailto:[email protected]> |
>>>> Twitter: @KSobkowiak
>>>> Calendar: http://goo.gl/yvsebC
>>>>
>>>>
>>>
>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> [email protected]
>> 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: [email protected] <mailto:[email protected]> |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC

Reply via email to