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

Re: Making ra_serf the default for DAV

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-10-19 19:02:05 CEST

justin.erenkrantz@gmail.com wrote on 10/19/2006 12:01:55 PM:

> On 10/19/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> > I'm also not comfortable with us shipping it as the default DAV
> > implementation until we get things like Digest Auth and GSSAPI working
> > at least as well as they do in Neon.
>
> So, there's a difference between shipping it and making it our default
in trunk.
>
> It's kind of sitting on a chicken-and-egg requirement: if folks start
> to use it more, ra_serf will get more attention and it's more likely
> to get those features; but if we won't adopt it until it is
> feature-complete, I'm not sure I'll have the incentive to finish it up
> as it seems we're constantly playing 'fetch me a rock' with vague
> promises to switch as people add more things to my plate that I must
> do to consider switching the default in trunk.
>
> So, would we be willing to switch the default in trunk say next month?
> I'll do my best to get the Win32 stuff straightened out by then, but
> I can't commit to anything else before then. But, I really think it's
> good enough to start having this conversation.
>
> 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

I think these are good points and this sounds like a good plan. I think
the somewhat justified fear is that even if this is made the default in
trunk there are a lot of authentication/proxy scenarios that Neon supports
that will not be tested and will surface post release.

I think that we should try to post Serf/Neon versions of the Win32
binaries. Perhaps with Serf the default and Neon in a special download.
At least it gives us options if problems surface.

Finally, when we do produced a release tarball should we start collecting
Serf/Neon information in the signatures and have any kind of
signature/testing requirement? Or if we declare Serf is the default,
require that all signatures are produced from that?

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 19 19:05:48 2006

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