On Thu, Jul 30, 2020 at 3:19 PM Daniel Ruggeri <dan...@bitnebula.com> wrote:
> > On 7/30/2020 2:41 PM, William A Rowe Jr wrote: > > On Thu, Jul 30, 2020 at 10:10 AM Jim Jagielski <j...@jagunet.com> wrote: > >> >> > On Jul 30, 2020, at 5:55 AM, Christophe JAILLET < >> christophe.jail...@wanadoo.fr> wrote: >> > >> > I wouldn't say it is a show stopper, but I thought that we had a travis >> job for that. >> > Apparently, it is on trunk only (see r1879370 which is not backported, >> maybe on purpose) >> >> I agree that it's not a show-stopper but it is something that seems easy >> to fix and, considering that (1) we want to release the best possible >> version as we can and (2) there is quite a bit of time between releases, I >> wouldn't be opposed if the RM decided to skip 2.4.45 and go w/ 2.4.46. >> > > Agreed. And Steffen points out there is precedence. > > Aye - and I'd hate to appear inconsistent :-) > > Version numbers are cheap - I'll re-roll when we have confirmation all is > good in the 2.4 branch. > Released on Jun 29th, we do not compile against lua 5.4.0. A possible fix is described here; https://github.com/apache/httpd/pull/133 If there is anyone very savvy with lua coding, it would be good to identify the best approach for compatibility. (It may not be realistic to solve this in 2.4.46.)
