Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of gstein@gmail.com designates
 74.125.82.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <51ACB7F5.3030004@collab.net>
References: <51ACA6B1.2010907@collab.net>
	<51ACB3BB.5040200@apache.org>
	<51ACB7F5.3030004@collab.net>
Date: Mon, 3 Jun 2013 12:53:12 -0400
Message-ID: 
 <CABD8fLWnW4+O8+730O0DWArCT-BF_Wsb=nco+JhK=beQ4eZApQ@mail.gmail.com>
Subject: Re: Serf issue #102 and 1.8.0 release timing
From: Greg Stein <gstein@gmail.com>
To: "C. Michael Pilato" <cmpilato@collab.net>
Cc: =?UTF-8?Q?Branko_=C4=8Cibej?= <brane@apache.org>,
	dev@subversion.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Lieven produced a short list of changes to release in 1.2.1, which I'm
merging now. The release should be done in about an hour.

Cheers,
-g


On Mon, Jun 3, 2013 at 11:36 AM, C. Michael Pilato <cmpilato@collab.net> wr=
ote:
> On 06/03/2013 11:18 AM, Branko =C4=8Cibej wrote:
>> I think it's clear that we have to wait for a Serf bugfix release before
>> releasing RC3, and during that time our soak period is simply on hold.
>> What happens after Serf 1.2.1 is released depends on the changes there.
>> If it's just a trivial bugfix for the digest authn issue, then we can
>> simply continue our soak (of which there are, IIRC, another two weeks).
>> If not -- then we're faced with a significant change in a non-optional
>> dependency and I can't think we can wiggle our way out of restarting the
>> soak in that case.
>
> FWIW, I am of the same mind.  So far, the 1.2.x branch on Serf contains t=
he
> following changes made since the 1.2.0 release itself:
>
> {{{
> ------------------------------------------------------------------------
> r1881 | chemodax | 2013-05-31 09:21:20 -0400 (Fri, 31 May 2013) | 2 lines
>
> Merge r1880 from trunk: Fix build with old Windows Platform SDK (issue #1=
00)
>
> ------------------------------------------------------------------------
> r1868 | chemodax | 2013-05-21 06:16:59 -0400 (Tue, 21 May 2013) | 7 lines
>
> On 1.2.x branch.
>
> Merge r1819 from trunk:
>   SPNego authentication optimization.
> Justification:
>   Avoid lookup through response headers on every read.
>
> ------------------------------------------------------------------------
> r1865 | lieven.govaerts@gmail.com | 2013-05-20 10:16:16 -0400 (Mon, 20 Ma=
y
> 2013) | 10 lines
>
> On the 1.2.x branch:
> Fix issue in serfmake where serf-1.pc is only created when explicitly inv=
oking
> 'serfmake build', not when going directly to 'serfmake install'.
>
> Applied directly to this branch as serfmake was removed from trunk.
>
> Patch by: Gabriela Gibson
>
> * serfmake: Add .pc file as build target for the install command.
>
> ------------------------------------------------------------------------
> r1864 | lieven.govaerts@gmail.com | 2013-05-20 09:44:26 -0400 (Mon, 20 Ma=
y
> 2013) | 8 lines
>
> On the 1.2.x branch:
> Fix issue #95 by applying the patch attached to that issue.
> Applied directly to this branch as the autoconf build files were removed
> from trunk.
>
> Patch by: Andreas Stieger
>
> * configure.in: Add gssapi option to build Kerberos/Negotiate authn modul=
e.
>
> ------------------------------------------------------------------------
> r1805 | chemodax | 2013-04-23 12:11:11 -0400 (Tue, 23 Apr 2013) | 2 lines
>
> Merge r1804 from trunk: Improve diagnostic of SSPI authentication failure=
s.
>
> }}}
>
> It's not a great deal of change[1] in terms of code churn, and the fix fo=
r
> issue #102 itself wasn't really all that complicated either.  Fortunately=
,
> we have the advantage that most of the Serf developership consists of
> Subversioneers -- so I'll defer the "destabilizing or not" determination =
to
> those guys.
>
> -- C-Mike
>
> [1] svn diff --old http://serf.googlecode.com/svn/tags/1.2.0 \
>             --new http://serf.googlecode.com/svn/branches/1.2.x
> [2] https://code.google.com/p/serf/source/detail?r=3D1885
>
> --
> C. Michael Pilato <cmpilato@collab.net>
> CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development
>