Re: Making ra_serf the default for DAV

On 10/19/06, Justin Erenkrantz <justin@erenkrantz.com> wrote:

> We can try it as the default for a few months, then we can then
> evaluate its stability and feature set when we're ready to consider
> starting the 1.5.x series. If we don't have all of the features we
> want by the time we start 1.5.x, then we can simply rollback the
> default to ra_dav for 1.5.x. -- justin

A big difference between this and, say, making fsfs the default in 1.2
was that 1.1 shipped with a "feature-complete" version of fsfs and
explicitly told people to try to use it, whereas the 1.4 ra_serf is
not feature complete and is probably not being used by anyone who
isn't an svn developer.

To be really conservative, we perhaps should release 1.5 with "serf
works great, please try it" and if all's well, 1.6 with "serf is the
default".

However, that's really slow. Maybe we could somehow get a
"feature-complete" ra_serf version out earlier, either by choosing to
backport all (compatible) ra_serf changes to 1.4.2, or by somehow
emphasizing that people should really really really test 1.5.0rc1 with
ra_serf in production-like environments.

--dave

-- 
David Glasser | glasser_at_mit.edu | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org