[Greg Stein]
> But I'll go one step further: you shouldn't care at all.
>
> I could release 1.2.2 tomorrow with all kinds of crap. Or maybe the
> day after 1.8.0 goes final. Not much you can do about it. Subversion
> needs to soak its own code, not the entire dependency stack.
You could, but 1.2
On Mon, Jun 3, 2013 at 10:22 AM, C. Michael Pilato wrote:
>...
> On the other hand, Serf 1.2.0 is the only available public Serf release with
> which Subversion 1.8.0 can operate[2], which really rather limits folks'
>...
> Unfortunately, there is as yet no public Serf release to date which contai
Belay that. I merged a couple extra things in the test suite, and
dropped one (just dealing with fixing a couple compiler warnings).
I'm going to wait for Lieven's +1 before cutting a release.
Cheers,
-g
On Mon, Jun 3, 2013 at 12:53 PM, Greg Stein wrote:
> Lieven produced a short list of chang
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 wrote:
> On 06/03/2013 11:18 AM, Branko Čibej wrote:
>> I think it's clear that we have to wait for a Se
On 06/03/2013 11:18 AM, Branko Čibej 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 f
On Mon, Jun 3, 2013 at 8:18 AM, Branko Čibej 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
On Mon, Jun 3, 2013 at 7:22 AM, C. Michael Pilato wrote:
> I'll suggest that the answer is found in how we'd track the issue locally.
> "Subversion requires Serf 1.2.1" would be a reasonable issue description.
> It would naturally be a 1.8.0 blocking issue. It's resolution (on our end,
> at least
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 contin
Last week it was discovered that Serf 1.2.0 broke support for Digest
authentication, at least for applications such as Subversion where a
connection might be used for multiple requests against different URLs. You
can read about the problem in the issue where it was tracked (Serf issue
#102 [1]) an
9 matches
Mail list logo
