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/07/05 15:43:30 UTC

Time for 2.4.34?

Seems to me that we are just about due for a 2.4.34 release...
Anyone opposed? I volunteer to RM.

Re: Time for 2.4.34?

Posted by Alain Toussaint <al...@vocatus.pub>.
Le jeudi 05 juillet 2018 à 11:43 -0400, Jim Jagielski a écrit :
> Seems to me that we are just about due for a 2.4.34 release...
> Anyone opposed? I volunteer to RM.

+1, don't wait for my LFS patch. I'll submit for >2.4.34 (.35 or more).

Alain

Re: Time for 2.4.34?

Posted by Daniel Ruggeri <dr...@primary.net>.
On 2018-07-05 10:43, Jim Jagielski wrote:
> Seems to me that we are just about due for a 2.4.34 release...
> Anyone opposed? I volunteer to RM.

+1

Do let me know if any of the scripts behave poorly for you. One thing 
worth noting, if your local server isn't configured to send emails 
through the ASF relays, announcements generated by the scripts may not 
be delivered.
-- 
Daniel Ruggeri

Re: Time for 2.4.34?

Posted by Stefan Eissing <st...@greenbytes.de>.
+1

Thanks Jim!

> Am 05.07.2018 um 17:43 schrieb Jim Jagielski <ji...@jaguNET.com>:
> 
> Seems to me that we are just about due for a 2.4.34 release...
> Anyone opposed? I volunteer to RM.


Re: Time for 2.4.34?

Posted by Graham Leggett <mi...@sharp.fm>.
On 05 Jul 2018, at 5:43 PM, Jim Jagielski <ji...@jaguNET.com> wrote:

> Seems to me that we are just about due for a 2.4.34 release...
> Anyone opposed? I volunteer to RM.

+1, and thank you.

Regards,
Graham
—


Re: Time for 2.4.34?

Posted by Jim Jagielski <ji...@jaguNET.com>.
My plan is to T&R sometime Tues or Weds... to ensure that everyone has had
enough time for a Head's Up and to bring up issues/concerns.

> On Jul 5, 2018, at 3:39 PM, Plüm, Rüdiger, Vodafone Group <ru...@vodafone.com> wrote:
> 
> 
> 
>> -----Ursprüngliche Nachricht-----
>> Von: Yann Ylavic <yl...@gmail.com>
>> Gesendet: Donnerstag, 5. Juli 2018 21:34
>> An: httpd-dev <de...@httpd.apache.org>
>> Betreff: Re: Time for 2.4.34?
>> 
>> On Thu, Jul 5, 2018 at 9:11 PM, Yann Ylavic <yl...@gmail.com>
>> wrote:
>>> On Thu, Jul 5, 2018 at 5:43 PM, Jim Jagielski <ji...@jagunet.com> wrote:
>>>> Seems to me that we are just about due for a 2.4.34 release...
>>>> Anyone opposed? I volunteer to RM.
>>> 
>>> +1, thanks Jim.
>> 
>> Possibly someone for the last vote on r1588806?
>> This simple change can avoid hard to diagnose bugs, with very little
>> risk IMO.
> 
> Done. r1835177.
> 
> Regards
> 
> Rüdiger


AW: Time for 2.4.34?

Posted by Plüm, Rüdiger, Vodafone Group <ru...@vodafone.com>.

> -----Ursprüngliche Nachricht-----
> Von: Yann Ylavic <yl...@gmail.com>
> Gesendet: Donnerstag, 5. Juli 2018 21:34
> An: httpd-dev <de...@httpd.apache.org>
> Betreff: Re: Time for 2.4.34?
> 
> On Thu, Jul 5, 2018 at 9:11 PM, Yann Ylavic <yl...@gmail.com>
> wrote:
> > On Thu, Jul 5, 2018 at 5:43 PM, Jim Jagielski <ji...@jagunet.com> wrote:
> >> Seems to me that we are just about due for a 2.4.34 release...
> >> Anyone opposed? I volunteer to RM.
> >
> > +1, thanks Jim.
> 
> Possibly someone for the last vote on r1588806?
> This simple change can avoid hard to diagnose bugs, with very little
> risk IMO.

Done. r1835177.

Regards

Rüdiger

Re: Time for 2.4.34?

Posted by Yann Ylavic <yl...@gmail.com>.
On Thu, Jul 5, 2018 at 9:11 PM, Yann Ylavic <yl...@gmail.com> wrote:
> On Thu, Jul 5, 2018 at 5:43 PM, Jim Jagielski <ji...@jagunet.com> wrote:
>> Seems to me that we are just about due for a 2.4.34 release...
>> Anyone opposed? I volunteer to RM.
>
> +1, thanks Jim.

Possibly someone for the last vote on r1588806?
This simple change can avoid hard to diagnose bugs, with very little risk IMO.

Re: Time for 2.4.34?

Posted by Yann Ylavic <yl...@gmail.com>.
On Thu, Jul 5, 2018 at 5:43 PM, Jim Jagielski <ji...@jagunet.com> wrote:
> Seems to me that we are just about due for a 2.4.34 release...
> Anyone opposed? I volunteer to RM.

+1, thanks Jim.

Re: Time for 2.4.34?

Posted by William A Rowe Jr <wr...@rowe-clan.net>.
I can get their efforts committed late this evening, if nobody beats me to
it. Expect to need a bit of crlf tweaking.

On Thu, Jul 5, 2018, 12:36 Marion et Christophe JAILLET <
christophe.jaillet@wanadoo.fr> wrote:

> +1, but latest zh-cn and zh-tw translation of error pages should be
> included IMHO.
>
> I've pushed for including what was already in trunk, but Codeingboy and
> popcorner have made improvements since the backport. (see docs@ ML)
>
> Not sure to have time tonight to push it on trunk and propose for backport.
> And, after tonight, I won't be able before monday evening.
>
> CJ
>
>
> Le 05/07/2018 à 17:43, Jim Jagielski a écrit :
> > Seems to me that we are just about due for a 2.4.34 release...
> > Anyone opposed? I volunteer to RM.
> >
>
>

Re: Time for 2.4.34?

Posted by Marion et Christophe JAILLET <ch...@wanadoo.fr>.
+1, but latest zh-cn and zh-tw translation of error pages should be 
included IMHO.

I've pushed for including what was already in trunk, but Codeingboy and 
popcorner have made improvements since the backport. (see docs@ ML)

Not sure to have time tonight to push it on trunk and propose for backport.
And, after tonight, I won't be able before monday evening.

CJ


Le 05/07/2018 à 17:43, Jim Jagielski a écrit :
> Seems to me that we are just about due for a 2.4.34 release...
> Anyone opposed? I volunteer to RM.
>