camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Whytock <dwhyt...@gmail.com>
Subject Re: [DISCUSS] Closing down for the 2.8.0 release
Date Thu, 30 Jun 2011 16:36:30 GMT
https://issues.apache.org/jira/browse/CAMEL-3948

On Thu, Jun 30, 2011 at 12:35 PM, Donald Whytock <dwhytock@gmail.com> wrote:
> Just a reminder...CAMEL-3948 is marked as fixed, but the current trunk
> still needs my final patch.
>
> Don
>
> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste Onofré <jb@nanthrax.net> wrote:
>> Hi Claus,
>>
>> Regarding Karaf 2.2.2, I've released OPS4J dependencies yesterday. Jamie
>> will cut off the release this afternoon.
>>
>> Regards
>> JB
>>
>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
>>>
>>> Hi
>>>
>>> Okay the JIRA roadmap for Camel 2.8 seems good now. There is 2 open
>>> tickets.
>>> - https://issues.apache.org/jira/browse/CAMEL-3774
>>> - https://issues.apache.org/jira/browse/CAMEL-4144
>>>
>>> CAMEL-3774 is about generating the manual and is assigned to Hadrian.
>>>
>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release is in progress.
>>> So by good chance we should be able to pickup that version when its
>>> released.
>>> Alternatively we can stick to Karaf 2.2.1 which works fine.
>>> (CAMEL-4144 is about some maven validate goal that would require Karaf
>>> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf is
>>> absolutely fine)
>>>
>>> The CI servers also seems good. Although they tend to run out of
>>> memory at the end, such as when testing the examples. But those are
>>> the last piece of the build, and thus all components tests fine.
>>>
>>> I suggest that when Karaf 2.2.2 is out we git it a few spins on the CI
>>> servers and then start cutting the Camel 2.8 release. Would be good to
>>> get it out before the summer vacation starts. As well its more than 3
>>> months since Camel 2.7 was released.
>>>
>>>
>>>
>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus Ibsen<claus.ibsen@gmail.com>
>>>  wrote:
>>>>
>>>> Hi
>>>>
>>>> Okay we should really start focusing on getting the last tickets which
>>>> has been assigned for 2.8 release done now.
>>>> There is about 350 tickets on the roadmap, so its going to be the
>>>> biggest release, since 2.0 went GA.
>>>>
>>>> So please take a look at your assigned tickets and get them done, or
>>>> move them for 2.9.
>>>> Then keep eyes on CI servers and help fix any test failures, so we
>>>> have green builds.
>>>>
>>>> The summer vacation period is approaching so we should IMHO get the
>>>> 2.8 release out early next month if possible.
>>>>
>>>>
>>>> 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