camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: [DISCUSS] Closing down for the 2.8.0 release
Date Sat, 18 Jun 2011 08:04:04 GMT
On Sat, Jun 18, 2011 at 1:08 AM, Donald Whytock <dwhytock@gmail.com> wrote:
> I've got a patch to contribute for camel-mail.  Is there still time to
> get that in?
>

Yeah try to get the patch by start of next week at the latest.

> Don
>
> On Thu, Jun 16, 2011 at 2:48 AM, Jean-Baptiste Onofré <jb@nanthrax.net> wrote:
>> Hi Claus,
>>
>> +1 to release Camel 2.8.0. I'm working on ServiceMix components using Camel
>> 2.8-SNAPSHOT, so I'm quite ready to integrate Camel 2.8.0 in ServiceMix :)
>>
>> Thanks,
>> Regards
>> JB
>>
>> On 06/16/2011 07:44 AM, Claus Ibsen wrote:
>>>
>>> Hi
>>>
>>> Could you take a look at the assigned tickets you have which is
>>> targeted for Camel 2.8.0 and get those resolved in due time.
>>>
>>> In terms of the CXF blueprint namespace handler, I have created
>>> sub-tickets for the remaning work which can be postponed to Camel 2.9.
>>> So we only need to add a bit of documentation of this new feature.
>>>
>>> CXF 2.4.1 has been updated so we are good there.
>>>
>>> In terms of Karaf, we should be able to run on Karaf 2.2.1. Our osgi
>>> tests runs on that version.
>>>
>>> So lets try to get the last tickets resolved, so we are in shape for
>>> cutting a release later this month. Would be good to get this big
>>> Camel 2.8 release out before the summer vacation start to hit us.
>>>
>>> Hadrian what does your time schedule look like? Do you have time to
>>> cut a release, if possible (fingers crossed), sometime next week. Or
>>> the week thereafter?
>>>
>>>
>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hzbarcea@gmail.com>
>>>  wrote:
>>>>
>>>> Hi,
>>>>
>>>> I would propose starting to close down and prepare for the 2.8.0 release
>>>> in
>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are will be
>>>> over 300 by the release time, probably setting a new record.
>>>>
>>>> As of now there are 17 issues unresolved, a few of them almost done, so
>>>> by
>>>> next week I assume there'll be significantly less. I would suggest
>>>> shifting
>>>> the focus from adding new features to stabilizing the build. If there are
>>>> any issues you know of that you think absolutely must be in 2.8.0 please
>>>> shout and ask for help if needed (especially non committers subscribing
>>>> to
>>>> this list).
>>>>
>>>> Thoughts?
>>>>
>>>> Hadrian
>>>>
>>>
>>>
>>>
>>
>



-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Mime
View raw message