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

Re: svn commit: rev 2521 - trunk/subversion/libsvn_client

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-07-15 21:58:52 CEST

Greg Stein <gstein@lyra.org> writes:

> On Mon, Jul 15, 2002 at 02:24:44PM -0500, Karl Fogel wrote:
> > Philip Martin <philip@codematters.co.uk> writes:
> > > I see a subpool being cleared at libsvn_client/commit.c:942, that's
> > > probably it. Putting my release-manager hat on (hmm, it doesn't seem
> > > to fit...) this code doesn't yet fix any locking bugs, so alpha is
> > > probably not the place to test it :-/
> >
> > :-)
> >
> > Ben's reverting it all right now.
> Can we be sure to get the right changes? It would suck to revert something
> that was a true bug fix. Or to pull something out that should stay in. Or
> revert it back to some code that was buggy. Or...
> I'm still of a mind to move *forward*, than to back it out.
> It sounds like Philip was close. I say that we let him stabilize the code
> and then we release Alpha.

I get the impression that Philip is worried (as are we) that the new
infrastructure introduces a whole new slew of yet-undiscovered bugs.
And he doesn't want to take all the blame for a buggy Alpha. :-)

The question is: how long do we wait? And if we do wait, maybe it
makes more sense to stabilize the access-baton stuff on a branch?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 15 22:00:55 2002

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.