Including serf 0.2 in svn 1.5 RC's

It looks like we will not be able to release serf 0.2 in the next coming
weeks. The code itself is ready, this is mainly an
availability-of-people issue. We hope to get it released at ApacheCon
(april 9th - 11th).

Now, what has this to do with Subversion? Serf 0.2 will include a whole
list of fixes and features that are needed to get ra_serf closer to
ra_neon in terms of functionality and stability. There's at least NTLM,
proxy server, progress feedback and SSL server certificate validation
that ra_serf will support with serf 0.2.

Wile subversion 1.5 beta contains most of the above (except ssl server
certificates), the code is only built when using serf trunk.

So, this leads me to the question: if we release serf 0.2 somewhere mid
april, when subversion 1.5 RC1 is probably already tagged, are there any
objections to start supporting serf 0.2 in a later RC and include it in
the deps file?

Considering serf is still listed as experimental I don't think this is a
big issue, but I'd like to hear other opinions too.

Lieven

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-20 12:59:26 CET