You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Jim Jagielski <ji...@jaguNET.com> on 2018/05/01 21:15:54 UTC

time for 2.4.34?

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...?

I offer to RM using Daniel's updated release scripts so
we can get a different set of eyes using the scripts.

Re: time for 2.4.34?

Posted by Stefan Eissing <st...@greenbytes.de>.
+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 <ji...@jaguNET.com>:
> 
> 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...?
> 
> I offer to RM using Daniel's updated release scripts so
> we can get a different set of eyes using the scripts.

Re: time for 2.4.34?

Posted by Jim Jagielski <ji...@jaguNET.com>.
Yes, for sure :)

> On May 1, 2018, at 9:32 PM, Alain Toussaint <al...@vocatus.pub> 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?

Posted by Alain Toussaint <al...@vocatus.pub>.
Le mardi 01 mai 2018 à 17:15 -0400, Jim Jagielski a écrit :
> 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...?
> 
> I offer to RM using Daniel's updated release scripts so
> we can get a different set of eyes using the scripts.

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?

Posted by Yann Ylavic <yl...@gmail.com>.
On Tue, May 1, 2018 at 11:15 PM, Jim Jagielski <ji...@jagunet.com> 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, the OP reports an
issue on slotmems after an upgrade from 2.2 to 2.4 (slotmems didn't
exist in 2.2, and the mod_proxy_lb quite changed in between).
Also, it looks more like an IPC-SysV "limitation" (on some Solaris
version?) than a bug in our code, maybe should we consider a move to
POSIX sems by default in trunk/2.next?
By the way, I modified the tool (attached in bz) to show what I
suspect are spurious collisions in ftok()+semget() with the OP's
balancers' names, but he switched to POSIX sems so I'm not sure he
will test any further. Possibly Rainer could try to run it on his
Solaris(es) to confirm or not (no specific version mentioned in
bz...).

> as well as a limited number of "other" changes to the
> codebase, maybe now is a Good Time to consider a 2.4.34...?

+1, once these are addressed.

>
> I offer to RM using Daniel's updated release scripts so
> we can get a different set of eyes using the scripts.

Thanks!


Regards,
Yann.

Re: time for 2.4.34?

Posted by Joe Orton <jo...@redhat.com>.
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...?
> 
> I offer to RM using Daniel's updated release scripts so
> we can get a different set of eyes using the scripts.

Thanks Jim that sounds good.

FYI on the mod_ssl vhost fix, Fedora users are giving +ve feedback from 
testing that patch - https://bugzilla.redhat.com/show_bug.cgi?id=1564537

Regards, Joe

Re: time for 2.4.34?

Posted by Graham Leggett <mi...@sharp.fm>.
On 01 May 2018, at 11:15 PM, Jim Jagielski <ji...@jaguNET.com> 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...?
> 
> I offer to RM using Daniel's updated release scripts so
> we can get a different set of eyes using the scripts.

+1, and thank you for this.

Regards,
Graham
—