Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of richardkettelerij@gmail.com
 designates 209.85.161.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGB5yN=1u=rfsbw389HbDp2Ln1dc4jGdb31geL8D9DHZEK2H+w@mail.gmail.com>
References: <4DF0C0E5.8070806@gmail.com>
 <BANLkTimRLOYrrs7OZFtTrTRNQ2TD-a-xyA@mail.gmail.com>
 <BANLkTi=oMPSk4MYNniCMybof7=c6rai_6w@mail.gmail.com>
 <4E0C1BBA.3070801@nanthrax.net>
 <BANLkTimRMAB7Hss-os7e=NE=hrjSTvsd8A@mail.gmail.com>
 <BANLkTi=AhoMWbG4tcz2=MOOhhqY7D5d=nQ@mail.gmail.com>
 <4E0D39FC.6000204@gmail.com> <4E128EF9.2040806@gmail.com>
 <4E13C3CA.7070601@gmail.com>
 <4E13F8C4.2090700@die-schneider.net> <4E151697.1080303@gmail.com>
 <4E1613DD.6070307@gmail.com>
 <CAGB5yNmNjfS12MZt7kRMYbPzDF9jipEgNUkfrHHr13rJ2FzKEw@mail.gmail.com>
 <CAGB5yN=1u=rfsbw389HbDp2Ln1dc4jGdb31geL8D9DHZEK2H+w@mail.gmail.com>
From: Richard Kettelerij <richardkettelerij@gmail.com>
Date: Tue, 12 Jul 2011 22:00:11 +0200
Message-ID: 
 <CAE+mP=r6QGA9_n4c0pE=M-V+1SudsHdwZGu0T5+HkMd1WoX8pw@mail.gmail.com>
Subject: Re: [DISCUSS] Closing down for the 2.8.0 release
To: dev@camel.apache.org
Content-Type: multipart/alternative; boundary=001517478f1484e4b304a7e4c002

--001517478f1484e4b304a7e4c002
Content-Type: text/plain; charset=ISO-8859-1

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

--001517478f1484e4b304a7e4c002--