[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Our (in)ability to do releases?

From: Daniel Berlin <dberlin_at_dberlin.org>
Date: 2006-07-10 16:37:51 CEST

Garrett Rooney wrote:
> On 7/9/06, Daniel Berlin <dberlin@dberlin.org> wrote:
>> Sorry, I don't believe this at all. All the time we've spent has been
>> waiting for RC's to be rolled and getting signatures, not waiting for
>> features to be fixed.
> Well, yes and no. We've certainly burned a lot of time on that, but
> we've also burned a lot of time waiting for BDB 4.4 fixes (and for
> someone not very familiar with that code (uhh, me) to get up to speed
> enough with it to finish those fixes off), something that IMO is
> likely to happen more and more as we go down the road of having
> multiple implementations of a given subsystem.

However, this is also going to get worse because we have a policy of
backwards compat with things like the fs until the "mythical 2.0", which
nobody seems to have any concrete idea of (IE what it would take to make
something 2.0).

This means we can't deprecate things as they fall by the wayside, even
if we had a strategy of waiting until the release was no longer
officially supported to remove the feature.

Not that i'm suggesting removing BDB right now, i'm just saying that
*even if we wanted to*, we don't have a policy about how to do it, other
than "we can't remove it until 2.0".

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 10 16:38:44 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.