You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Nic Jansma <ni...@nicj.net> on 2018/02/13 18:23:42 UTC
Re: Time for 2.4.30? (Was: Re: 2.4.x STATUS needs you!)
Are there still plans to push for a 2.4.30 soon? There's a couple bug
fixes in it that I'd love to have in the official builds!
Thanks,
- Nic
On 2018/01/04 12:43:12, Jim Jagielski <j....@jaguNET.com> wrote:
> As we get settled into the new year, it seems a good time>
> to think about a 2.4.30 release in the coming week or>
> so. Lots of good stuff currently in 2.4.30-dev and even>
> more good stuff in STATUS awaiting a single vote!>
>
> Let's see if we can clean-up STATUS, get 2.4.30-dev into>
> fantastic shape, and "commit" to doing a release no later>
> than mid Jan.>
>
> I volunteer to RM and/or help someone else RM.>
>
Re: Time for 2.4.30? (Was: Re: 2.4.x STATUS needs you!)
Posted by Graham Leggett <mi...@sharp.fm>.
On 14 Feb 2018, at 2:40 PM, Jim Jagielski <ji...@jaguNET.com> wrote:
> Yes... there are/were a few backports which are/were lacking
> a single vote…
We’re down to these ones left:
+1: jim, minfrin
+1: jailletc36, minfrin
+1: minfrin
Regards,
Graham
—
Re: Time for 2.4.30? (Was: Re: 2.4.x STATUS needs you!)
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
And perhaps sufficient testing of the end result? The number of exceptions
at the moment bode ill for a stable long term release. Feature dumps always
introduce instability.
Maybe a bug fix only freeze for a short period to stabilize that pile of
code?
On Feb 14, 2018 06:41, "Jim Jagielski" <ji...@jagunet.com> wrote:
> Yes... there are/were a few backports which are/were lacking
> a single vote...
>
> On Feb 13, 2018, at 1:23 PM, Nic Jansma <ni...@nicj.net> wrote:
>
> Are there still plans to push for a 2.4.30 soon? There's a couple bug
> fixes in it that I'd love to have in the official builds!
>
> Thanks,
>
> - Nic
>
> On 2018/01/04 12:43:12, Jim Jagielski <j....@jaguNET.com>
> <j....@jaguNET.com> wrote:
> > As we get settled into the new year, it seems a good time>
> > to think about a 2.4.30 release in the coming week or>
> > so. Lots of good stuff currently in 2.4.30-dev and even>
> > more good stuff in STATUS awaiting a single vote!>
> >
> > Let's see if we can clean-up STATUS, get 2.4.30-dev into>
> > fantastic shape, and "commit" to doing a release no later>
> > than mid Jan.>
> >
> > I volunteer to RM and/or help someone else RM.>
> >
>
>
>
Re: Time for 2.4.30? (Was: Re: 2.4.x STATUS needs you!)
Posted by Jim Jagielski <ji...@jaguNET.com>.
Yes... there are/were a few backports which are/were lacking
a single vote...
> On Feb 13, 2018, at 1:23 PM, Nic Jansma <ni...@nicj.net> wrote:
>
> Are there still plans to push for a 2.4.30 soon? There's a couple bug fixes in it that I'd love to have in the official builds!
>
> Thanks,
>
> - Nic
>
> On 2018/01/04 12:43:12, Jim Jagielski <j....@jaguNET.com> <ma...@jaguNET.com> wrote:
> > As we get settled into the new year, it seems a good time>
> > to think about a 2.4.30 release in the coming week or>
> > so. Lots of good stuff currently in 2.4.30-dev and even>
> > more good stuff in STATUS awaiting a single vote!>
> >
> > Let's see if we can clean-up STATUS, get 2.4.30-dev into>
> > fantastic shape, and "commit" to doing a release no later>
> > than mid Jan.>
> >
> > I volunteer to RM and/or help someone else RM.>
> >