directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Custine" <>
Subject Re: [ApacheDS] Ramifications of removing configuration beans
Date Tue, 25 Sep 2007 18:17:32 GMT
See, this is something that I have never liked about the stable / unstable
release categorization...  How can we ever claim to have a stable
2.0release without some limitation of changes on the unstable
1.5 at some point?

My preference is to begin limiting major changes to 1.5.x for the sake of
stabilizing it to be the 2.0 stable release, and at that point we EOL 1.0.
We start the major refactorings in 2.5 based on the 2.0 or a late
1.5release.  I think anything else is just too complicated for us to


On 9/25/07, Alex Karasulu <> wrote:
> On 9/25/07, Emmanuel Lecharny <> wrote:
> >
> > For those reasons, I would say : keep 2.0 conf as is, and do
> > experimentations in a branch.
> So we're not going to be too free to experiment from now on in 1.5branch?  This sort
> breaks with our general policy on branches yet it's appealing in many
> other ways.  It's
> just a matter of trade offs.  It's more important in this case for us to
> just make a decision.
> Either option is fine with me since both choices take relatively the same
> time and energy.
> I started this thread to see what people are thinking about it and it
> sounds as though there
> is a split.  Perhaps we just need a vote and go with it.
> Alex

View raw message