Guillaume, you are obviously absolutely right. My bad.
Guillaume, you mention 1.6.x. Do you mean that we should not release
1.6.2 until osgi is fixed or we should not end support for 1.6.x until
this is fixed?
Hadrian
Begin forwarded message:
From: Guillaume Nodet <gno...@gmail.com>
Date: September 15, 2009 10:33:28 AM EDT
To: priv...@camel.apache.org
Subject: Re: [DISCUSS] Life expectancy for the camel-1.x branch
Reply-To: priv...@camel.apache.org
If possible, I'd like to fix the OSGi metadata for 1.6.x before
doing a release.
It would allow deploying camel 2.x and 1.x side by side in OSGi.
Also, why is this on private ? I think this should be discussed on
dev@ as there is nothing sensitive here.
On Tue, Sep 15, 2009 at 16:29, Hadrian Zbarcea <hzbar...@gmail.com>
wrote:
Hi,
With Camel 2.0 out and getting great traction, I believe it's time
to set an
end-of-life timeframe for Camel 1.x and what releases can be
expected.
My preference would be to make another release now, 75 fixes went
in since
the 1.6.1 release in May, and keep supporting the 1.x branch until
the end
of the year with another release in Dec or Jan, or through Q1 of
2010.
Any thoughts?
Hadrian
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
