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

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

From: Greg Stein <gstein_at_gmail.com>
Date: Thu, 3 Jan 2013 18:29:52 -0500

Eep! Didn't realize, or forgot, that I'm blocking the release.

Okay. I'll release 1.2 by Sunday.

Then I'd support Lieven's suggestion to make it the minimum for 1.8. I
would also recommend it as the suggested version for 1.7 (and keep 0.7 as
the minimum, I guess)

Cheers,
-g
On Jan 3, 2013 2:27 PM, "Lieven Govaerts" <lgo_at_apache.org> wrote:

> Hi Mike,
>
> In short: for me serf 1.2.0 should be the minimum version. Its release
> blocks on gstein for now, but I'm ready to release it in time for svn
> 1.8.0.
>
> On Thu, Jan 3, 2013 at 5:02 PM, C. Michael Pilato <cmpilato_at_collab.net>
> wrote:
> > 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).
>
> I don't think there will be a 1.1.2 release.
>
> > 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.
>
> Most of the changes planned for 1.2.0 where made based on
> issues/requests from the Subversion project. There are some changes,
> e.g. the Kerberos authentication handling, that are needed to make
> Subversion work in certain (esp. Windows) environments:
> https://code.google.com/p/serf/source/detail?r=1711
>
> > 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. :-)
>
> Well, you can also cough up $'s for gstein's bar tab, but I understand
> why you picked me! :)
>
> Anyways, my plan was to make serf 1.2.0 available when svn 1.8.x
> branches, or sooner. I'm waiting a bit with the release because Greg
> wants to review the new API first, so I hope he has some time soon.
>
> Lieven
>
Received on 2013-01-04 00:30:25 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.