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

What version of Serf will be the required minimum for Subversion 1.8?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Thu, 3 Jan 2013 11:02:28 -0500

Hey, all. I'd like to get a sense of what we're targeting in terms of
minimum required Serf library versions for Subversion 1.8.

First, the status quo:

- In Subversion 1.7, we require Serf 0.7.1 or better.
- Currently on the trunk, we require Serf 1.0.0 or better.

In reviewing the changes released in Serf since its 1.0.0 release (which is
everything up to and including the current 1.1.1 version), I see a number of
them that stand out as must-haves for Subversion's needs, especially as
ra_serf becomes the sole DAV RA implementation. I also examined the
as-yet-unreleased changes currently queued for Serf 1.1.2, but don't spot
anything that's mission-critical there. So, at a minimum, I'd like to
propose that we further bump the minimum required Serf version to 1.1.1 on
trunk (and by extension, for Subversion 1.8).

Now, it appears that Lieven & Co. are prepping for a Serf 1.2.0 release
Soon(tm). There have been quite a few improvements made in 1.2.0 versus
1.1.0, but I didn't quickly spot any that screamed out
"omigosh-we-must-have-them-now-now-now!" Still, someone closer to the
project would be able to better evaluate whether 1.2.0 should instead be the
targeted requirement for Subversion 1.8.

Of course, 1.2.0 hasn't been released yet, so if that's our target, then
this community needs to recognize that we have a 1.8 blocker that's not
*directly* in our hands to control. We might have to start coughing up € to
pay Lieven's bar tab or something. :-)

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development

Received on 2013-01-03 17:03:05 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.