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

Re: Status of TODO-1.6

From: Lieven Govaerts <svnlgo_at_mobsol.be>
Date: Fri, 26 Dec 2008 20:32:50 +0100

Justin Erenkrantz wrote:
> On Fri, Dec 26, 2008 at 11:07 AM, Lieven Govaerts <svnlgo_at_mobsol.be> wrote:
>>> Lieven,
>>> Thanks for looking into this. Do we know if serf is planning a release so that
>>> users of 1.6 can get these bug fixes?
>> I've talked with Justin last weekend about this and we agreed on
>> releasing serf 0.3 before svn 1.6. Any idea when this is planned? In two
>> months or so?
> (Thanks as well for looking into it. Good to see it's likely been
> fixed. *grin*)
> In my mind, the big 'serf' question is whether the next release is
> going to be "1.0 or not" and 'freeze' the APIs. If Ben is still
> making immediate forward progress with the http-protocol v2 stuff,
> then I'm willing to give Ben a few weeks to see if he encounters
> anything that would necessitate changing the serf APIs. Unlikely, but
> I'd like to give that opportunity if something comes up.
> Anyone else have an opinion here? -- justin

Why not release serf 0.3 now, together with svn 1.6 and plan for serf
1.0 together with svn 1.7?

Before freezing the serf API, I'd like to see how we can move some of
the code in libsvn_ra_serf/util.c and libsvn_ra_serF/auth.c to serf. We
probably also have to implement/fix some of the outstanding TODO's
before we can make serf the default http library for svn. I'm not sure
we need API changes for those TODO's, but I'd like to still have the option.


Received on 2008-12-26 20:33:07 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.