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 Wed, 13 Jul 2011 13:48:08 GMT
On Wed, Jul 13, 2011 at 3:22 PM, Hadrian Zbarcea <hzbarcea@gmail.com> wrote:
> I am ready to start the 2.8.0 builds in about one hour. If you know of
> anything that still needs to be fixed please let me know asap.
>

I will commit a fix for
https://issues.apache.org/jira/browse/CAMEL-4222 in about 30 min when
the full unit test is complete.


> Cheers,
> Hadrian
>
>
> On 07/12/2011 11:03 PM, Hadrian Zbarcea wrote:
>>
>> I reviewed your patch and it looks ok, plus the change is pretty
>> isolated. If that's the only thing left to be done, please go ahead and
>> commit it. I started a fresh build over night. If all goes well, I'll
>> start building the 2.8.0 release in the morning.
>>
>> Hadrian
>>
>>
>> On 07/12/2011 04:00 PM, Richard Kettelerij wrote:
>>>
>>> I doubt if it would be wise to stall the release much longer. In terms of
>>> the number of tickets, 2.8.0 seems to be the biggest release yet. Also on
>>> June 9 Hadrian proposed to cut the release in 2-3 weeks, it's now over 4
>>> weeks since that post so the release is already a bit overdue.
>>>
>>> Nevertheless, would anyone what to see
>>> https://issues.apache.org/jira/browse/CAMEL-4093 included? I attached a
>>> patch a couple of weeks ago. It's not a big change and ready to be
>>> committed, but I have no problem with postponing it for 2.9.0.
>>>
>>> On Tue, Jul 12, 2011 at 3:25 PM, Claus Ibsen<claus.ibsen@gmail.com>
>>> wrote:
>>>
>>>> Hi
>>>>
>>>> So Camel 2.8.0 starts to look good.
>>>>
>>>> The last CI test at Apache had only 1 unit test failure which is a non
>>>> deterministic test that can fail for some strange reason.
>>>> https://builds.apache.org/job/Camel.trunk.fulltest/366/
>>>>
>>>> I also ran a local OSGi unit test this morning and they all passed.
>>>>
>>>> In terms of ticket outstanding in JIRA then there is only 2 left
>>>> https://issues.apache.org/jira/browse/CAMEL-3774
>>>> https://issues.apache.org/jira/browse/CAMEL-4189
>>>>
>>>> 3774: This is about generating the manual when doing the release. I
>>>> guess Hadrian haven't had a look at it. Since we are able to cut the
>>>> release, I guess this ticket may be able to postpone for Camel 2.9
>>>>
>>>> 4189: This is about a config.properties in the karaf. As I understand
>>>> this config.properties file is not part of the release in the kit or
>>>> in the maven repository. Its used for the karaf validate plugin, to
>>>> validate the features.xml file. Correct me if I am wrong. This could
>>>> be post poned to Camel 2.9.
>>>>
>>>> So from a JIRA point of view it seems good. Do anyone have any last
>>>> item tickets they would like addressed?
>>>>
>>>> I have two tickets which we can discuss whether we want to delay the
>>>> release to get included
>>>> https://issues.apache.org/jira/browse/CAMEL-4212
>>>> https://issues.apache.org/jira/browse/CAMEL-4202
>>>>
>>>> 4212 is about supporting multi value headers in the HTTP related
>>>> components. This may be a bit more work, so we may consider scheduling
>>>> this for Camel 2.9. This is discussed on the @dev forum.
>>>>
>>>> 4202 is being discussed on the @user forum. Its about making
>>>> request/reply over JMS with fixed replyTo queues faster. It could be
>>>> worthwhile for the ppl who uses JMS to participate in the @user
>>>> discussion so we are able to agree upon some solution.
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Jul 8, 2011 at 10:53 AM, Claus Ibsen<claus.ibsen@gmail.com>
>>>> wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> I just ran the osgi tests locally and stumbled across two issues
>>>>>
>>>>> 1)
>>>>> Some weird maven duplicate test set issue about FtpConsumerTest. So I
>>>>> disable that test to move on. I know the tests works fine when running
>>>>> it manually, eg from an IDE etc. Anyway the globe keep on turning and
>>>>> we can't be stuck fiddling with weird maven issues all day.
>>>>>
>>>>> 2)
>>>>> The MailRouteTest no longer works. I guess its due those recent
>>>>> changes in the Camel karaf feature.xml file. So I disabled the test.
>>>>> The test relies on that there is a Mocked JavaMail provider installed,
>>>>> that can act as the mail server. But it doesn't so it tries to connect
>>>>> to a local running mail server on port 25.
>>>>>
>>>>> All the other tests passed.
>>>>>
>>>>> So lets close down this baby so we can cut a release for an overdue
>>>>> release. We owe it to the community to bring out Camel 2.8.0 this
>>>>> summer :)
>>>>>
>>>>> --
>>>>> 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/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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/
>>>>
>>>
>



-- 
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