Re: locking branch progress report.

On 2004-12-16 09:08-0600, Ben Collins-Sussman wrote:
> Oops, I meant to send this to all of dev@.
>
> Begin forwarded message:
>
> >From: Ben Collins-Sussman <sussman@collab.net>
> >
> >On Dec 16, 2004, at 7:38 AM, Jani Averbach wrote:
> >
> >...doesn't work at all, as expected. I've not implemented RA->lock()
> >in ra_dav yet!
> >
> >Here's the state of locking right now:
> >
> > * BDB: done by sussman.
> > * FSFS: fitz is working on it.
> > * svnserve: done by lundblad.
> > * ra_svn: done by lundblad.
> > * mod_dav_svn: done by sussman.

The intresting thing is that the Apache was segfaulting, so even when
ra_dav is undone, we have a client side server exploit which could
bring down the server/mod_dav_svn.

This applies only of course in the case that mod_dav_svn is really
ready and done.

> > * ra_dav: NOT done. sussman is working on it.
> > * client changes: lundblad is working on it.
> > 'svn lock/unlock': done.
> > changes to 'svn up/commit': NOT done.
> > changes to 'svn info/status': NOT done.
> > svn:needs-lock property and ro/rw behaviors: NOT done.
> >
> >I don't think it makes much sense to run nightly regression tests on
> >the locking branch yet... not unless you run ra_svn/bdb only.
> >

Ok, I will probably disable ra_dav test for the present. Please let me
know when I should re-activate them.

BR, Jani

-- 
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org