Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of christian.mueller@gmail.com
 designates 209.85.216.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGB5yNmYBNyZoM0RMqTM0HKP3kGDUNuhGJzYa=3_DVy_Aijeow@mail.gmail.com>
References: 
 <CAGB5yNkJ5OngUmMu9ig6=xTds11xbv21FpauMRQMx9EECZtP8w@mail.gmail.com>
	<1322773777071-5039933.post@n5.nabble.com>
	<CAGB5yNkx2wgQ5=AYpvOmYvRxmHjZQQTr=e65MpqDZbqS-W7W5w@mail.gmail.com>
	<CALvzYd9S2EAmhc+s_4muief+992FRpb5RQ+1ahLto+AEQHwrMQ@mail.gmail.com>
	<CADHGh9UUsHzKsvPpN7qshOZUxZw=AqDzYTVLBuPw7w418Bj_sg@mail.gmail.com>
	<CAGB5yNmYBNyZoM0RMqTM0HKP3kGDUNuhGJzYa=3_DVy_Aijeow@mail.gmail.com>
Date: Wed, 7 Dec 2011 00:16:10 +0100
Message-ID: 
 <CALvzYd_Q=igHqnzWM+aYvPT1FD7SHOX9SoiVOEaGnFGEdHCzYw@mail.gmail.com>
Subject: Re: [DISCUSS] - Camel 2.9 release
From: =?ISO-8859-1?Q?Christian_M=FCller?= <christian.mueller@gmail.com>
To: dev@camel.apache.org
Content-Type: multipart/alternative; boundary=00163630f2a1ebd08104b3749e18

--00163630f2a1ebd08104b3749e18
Content-Type: text/plain; charset=ISO-8859-1

Windows build 137 didn't had the problem anymore to not be able to remove
camel-core-2.9-SNAPSHOT.jar. However, we have 9 failed unit tests
(camel-cxf, camel-jms and camel-stream) [1].

The new SMX OSGI bundles are in vote. Hopefully we will have the new
versions in a few days and upgrade our dependencies (I want to resolve
CAMEL-4721 and CAMEL-4675).

I also work on CAMEL-4734, but this is not a blocker for Camel 2.9.0 (could
be finished in 2.9.1 or 2.10.0).

[1]
https://builds.apache.org/view/A-F/view/Camel/job/Camel.trunk.fulltest.windows/137/

Best,
Christian


On Tue, Dec 6, 2011 at 9:38 AM, Claus Ibsen <claus.ibsen@gmail.com> wrote:

> Hi
>
> We should close done on JIRA tickets for Camel 2.9
>
> The current list is:
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CAMEL+AND+fixVersion+%3D+%222.9.0%22+AND+resolution+%3D+Unresolved
>
> I moved some tickets to Camel 2.10. I kinda afterwards forgot maybe
> they should have been assigned for 2.9.1.
> Anyway for the current list, couple people take a look and resolve
> your tickets, or postpone them to 2.9.1 or 2.10.
>
> The last CI test on trunk was a success
> https://builds.apache.org/job/Camel.trunk.fulltest/
>
> We should keep eyes on them. The Windows test still have an issue to
> test completely. Christian have posted on @dev about this and will get
> in touch with ASF infra.
>
>
> If the SMX team have any OSGi bundles about to be released. Then it
> would be great if they could do this ASAP. Then we could upgrade the
> Camel features to use those latest releases.
>
>
>
> On Mon, Dec 5, 2011 at 9:02 AM, Ioannis Canellos <iocanel@gmail.com>
> wrote:
> > Besides, the compile issues and breaking compatibility with karaf, cxf
> and
> > servicemix I think that upgrating spring to 3.1 also renders the RC
> totally
> > useless. People have downloaded it and prepared for it, we should avoid
> > having "surprises" in the actual release.
> >
> > --
> > *Ioannis Canellos*
> > *
> > FuseSource <http://fusesource.com>
> >
> > **
> > Blog: http://iocanel.blogspot.com
> > **
> > Apache Karaf <http://karaf.apache.org/> Committer & PMC
> > Apache Camel <http://camel.apache.org/> Committer
> > Apache ServiceMix <http://servicemix.apache.org/>  Committer
> > Apache Gora <http://incubator.apache.org/gora/> Committer
> > Apache DirectMemory <http://incubator.apache.org/directmemory/>
> Committer
> > *
>
>
>
> --
> 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/
>

--00163630f2a1ebd08104b3749e18--