It's useless to add fixes to a branch if we don't also release from
that branch eventually. Maintaining the 1.x branch takes some
commitment, time and energy. My question was about our commitment to
the community and what users could expect. For instance we could
agree that it does not make sense to put and test more patches (and
hence to release) on 1.x after some date, or we could say that 1.x is
still used by a large percentage of users and want to add patches
there for an undetermined time.
Not deciding on it now is an option, but I brought it up because at
some point we'll have to address it, I think.
Thanks
Hadrian
On Sep 15, 2009, at 10:49 AM, Guillaume Nodet wrote:
On Tue, Sep 15, 2009 at 16:44, Hadrian Zbarcea <hzbar...@gmail.com>
wrote:
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?
If we plan to do a release on the 1.6 branch, I'd like to have the
OSGi metadata fixed. I'm working on trunk today but I should be able
to backport it to 1.6 branch asap if there is a release planned soon.
But I have no strong opinion on an end-of-life of that branch. We
don't do minor releases often afaik and I'm not sure we really need to
make a decision about that.
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
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
