Re: [VOTE] Allow for defect fix releases at httpd

2018-05-02 Thread Nick Kew
> On 2 May 2018, at 15:45, Micha Lenk wrote: > > Hi Graham, > > On 05/01/2018 04:33 PM, Graham Leggett wrote: >> What has been missing is input from the major distributors of our >> software (Fedora, Ubuntu, Redhat, Debian, Apple, Windows, Linux from >> Scratch, etc), who I believe are probably

Re: [VOTE] Allow for defect fix releases at httpd

2018-05-02 Thread Jim Jagielski
> On May 2, 2018, at 10:45 AM, Micha Lenk wrote: > > Hi Graham, > > On 05/01/2018 04:33 PM, Graham Leggett wrote: >> What has been missing is input from the major distributors of our >> software (Fedora, Ubuntu, Redhat, Debian, Apple, Windows, Linux from >> Scratch, etc), who I believe are pro

Re: [VOTE] Allow for defect fix releases at httpd

2018-05-02 Thread Micha Lenk
Hi Graham, On 05/01/2018 04:33 PM, Graham Leggett wrote: What has been missing is input from the major distributors of our software (Fedora, Ubuntu, Redhat, Debian, Apple, Windows, Linux from Scratch, etc), who I believe are probably going “httpd is a mature project, we have nothing to worry abo

Re: time for 2.4.34?

2018-05-02 Thread Jim Jagielski
Yes, for sure :) > On May 1, 2018, at 9:32 PM, Alain Toussaint wrote: > > I promised a patch for BLFS layout and haven't delivered yet. Will the > release happen after > Thursday? (I'll take Thursday to deliver the layout patch). > > Alain

Re: time for 2.4.34?

2018-05-02 Thread Yann Ylavic
On Tue, May 1, 2018 at 11:15 PM, Jim Jagielski wrote: > Considering that we have some regressions in .33 which > will soon be fixed (these are the 2 noted ShowStoppers) The fix for PR 62308 is being tested and we should be good soon, I think. I don't think PR 62277 is a regression/showstopper, t

Re: time for 2.4.34?

2018-05-02 Thread Joe Orton
On Tue, May 01, 2018 at 05:15:54PM -0400, Jim Jagielski wrote: > Considering that we have some regressions in .33 which > will soon be fixed (these are the 2 noted ShowStoppers) > as well as a limited number of "other" changes to the > codebase, maybe now is a Good Time to consider a 2.4.34...? >

Re: time for 2.4.34?

2018-05-02 Thread Stefan Eissing
+1. Some h2 issues accumulated, just got confirmation on the keepalive fix and will propose for backport today. Nothing else in the pipe from me. > Am 01.05.2018 um 23:15 schrieb Jim Jagielski : > > Considering that we have some regressions in .33 which > will soon be fixed (these are the 2 no