Re: Serf issue #102 and 1.8.0 release timing

2013-06-03 Thread Greg Stein
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

Re: Serf issue #102 and 1.8.0 release timing

2013-06-03 Thread Greg Stein
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

Re: Serf issue #102 and 1.8.0 release timing

2013-06-03 Thread C. Michael Pilato
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

Re: Serf issue #102 and 1.8.0 release timing

2013-06-03 Thread Ben Reser
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

Re: Serf issue #102 and 1.8.0 release timing

2013-06-03 Thread Branko Čibej
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