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

Re: Issues with serf, scheduled for 1.7.0

From: Stefan Sperling <stsp_at_elego.de>
Date: Wed, 27 May 2009 19:36:26 +0100

On Wed, May 27, 2009 at 02:11:46PM -0400, Paul Burba wrote:
> Due to some problems with the dev_at_svn.t.o mailing list, Stefan
> Sperling can't create any new threads at the moment, so I'm doing it
> for him.

Thanks Paul!

*grabs mic*

Yes, jackr is investigating. For some reason the dev list does
not want mail from me unless an in-reply-to header pointing
to the dev list is set... or something... we still don't really know.

So what I wanted to say was this:

Just poking serf people:

There has been talk of making serf the default HTTP backend for 1.7.0.
It is the default in trunk right now, IIRC.

But there are two blocking issues for serf becoming the default
in 1.7.0, and nobody seems to be working on them:

#3375: ra_serf desperately needs an error handling overhaul
http://subversion.tigris.org/issues/show_bug.cgi?id=3375
(this one might be a bit of work)

#3301: Cannot build without OpenSSL
http://subversion.tigris.org/issues/show_bug.cgi?id=3301
(this one should be easy)

In case these issues aren't fixed, it looks like there will be vetos
for serf to become the default and we might have to flip the default
back to neon before release.

I'm not asking anyone in particular to fix these issues.
I'm just pointing this out so that there is no surprise late in the
game close before 1.7-release when this issue will come up again.

Because *now* is the time to fix bugs!
When we want to release it is too late to fix them, in a rush.

Stefan
Received on 2009-05-27 20:36:48 CEST

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