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/02/14 13:22:02 UTC
T&R of 2.4.30 Proposal
I propose a T&R of 2.4.30 on Feb 19th. I offer to RM
unless someone else would like to do so.
Re: T&R of 2.4.30 Proposal
Posted by Yann Ylavic <yl...@gmail.com>.
On Thu, Feb 15, 2018 at 3:17 PM, Jim Jagielski <ji...@jagunet.com> wrote:
>
>
>> On Feb 15, 2018, at 8:49 AM, Eric Covener <co...@gmail.com> wrote:
>>
>> On Thu, Feb 15, 2018 at 8:45 AM, Daniel Ruggeri <dr...@primary.net> wrote:
>>> As mentioned before, I actually want to RM, but am still waiting for *any* confirmation that the dead-on-the-vine 2.6 release I bundled is at least structurally correct and matches project expectations. Since releases of source are one of the few things the version control time machine cannot undo (and are sacred things to the ASF as well), I want to be sure of the procedure. Maybe instead of doing the RM job, I could talk you into putting the (presumably less) volunteer time to vetting out the previous work so we can add to the number of folks willing and comfortable being RM?
>>
>> I think it would be easier for someone to check your work on the 30th
>> 2.4.x release ather than a first 2.5/2.6 release. Also, more normal
>> testers. Just my 2c.
>>
>
> +1
+1, and +1 for Daniel to RM, thanks!
Re: T&R of 2.4.30 Proposal
Posted by Jim Jagielski <ji...@jaguNET.com>.
> On Feb 15, 2018, at 8:49 AM, Eric Covener <co...@gmail.com> wrote:
>
> On Thu, Feb 15, 2018 at 8:45 AM, Daniel Ruggeri <dr...@primary.net> wrote:
>> As mentioned before, I actually want to RM, but am still waiting for *any* confirmation that the dead-on-the-vine 2.6 release I bundled is at least structurally correct and matches project expectations. Since releases of source are one of the few things the version control time machine cannot undo (and are sacred things to the ASF as well), I want to be sure of the procedure. Maybe instead of doing the RM job, I could talk you into putting the (presumably less) volunteer time to vetting out the previous work so we can add to the number of folks willing and comfortable being RM?
>
> I think it would be easier for someone to check your work on the 30th
> 2.4.x release ather than a first 2.5/2.6 release. Also, more normal
> testers. Just my 2c.
>
+1
Re: T&R of 2.4.30 Proposal
Posted by Daniel Ruggeri <dr...@apache.org>.
On 2018/02/15 13:49:01, Eric Covener <co...@gmail.com> wrote:
> On Thu, Feb 15, 2018 at 8:45 AM, Daniel Ruggeri <dr...@primary.net> wrote:
> > As mentioned before, I actually want to RM, but am still waiting for *any* confirmation that the dead-on-the-vine 2.6 release I bundled is at least structurally correct and matches project expectations. Since releases of source are one of the few things the version control time machine cannot undo (and are sacred things to the ASF as well), I want to be sure of the procedure. Maybe instead of doing the RM job, I could talk you into putting the (presumably less) volunteer time to vetting out the previous work so we can add to the number of folks willing and comfortable being RM?
>
> I think it would be easier for someone to check your work on the 30th
> 2.4.x release ather than a first 2.5/2.6 release. Also, more normal
> testers. Just my 2c.
>
Well... When you say it like that it makes perfect sense, hahaha
I will proceed on Monday with T&R and call for vote.
Re: T&R of 2.4.30 Proposal
Posted by Yann Ylavic <yl...@gmail.com>.
On Thu, Feb 15, 2018 at 2:49 PM, Eric Covener <co...@gmail.com> wrote:
> On Thu, Feb 15, 2018 at 8:45 AM, Daniel Ruggeri <dr...@primary.net> wrote:
>>
>> Side note, the slotmem fix seems like a showstopper, right? I'd want to see that in before a T&R.
>
> +1
Done in r1824333.
Re: T&R of 2.4.30 Proposal
Posted by Eric Covener <co...@gmail.com>.
On Thu, Feb 15, 2018 at 8:45 AM, Daniel Ruggeri <dr...@primary.net> wrote:
> As mentioned before, I actually want to RM, but am still waiting for *any* confirmation that the dead-on-the-vine 2.6 release I bundled is at least structurally correct and matches project expectations. Since releases of source are one of the few things the version control time machine cannot undo (and are sacred things to the ASF as well), I want to be sure of the procedure. Maybe instead of doing the RM job, I could talk you into putting the (presumably less) volunteer time to vetting out the previous work so we can add to the number of folks willing and comfortable being RM?
I think it would be easier for someone to check your work on the 30th
2.4.x release ather than a first 2.5/2.6 release. Also, more normal
testers. Just my 2c.
> Side note, the slotmem fix seems like a showstopper, right? I'd want to see that in before a T&R.
+1
Re: T&R of 2.4.30 Proposal
Posted by Jim Jagielski <ji...@jaguNET.com>.
++1 on you RMing!
> On Feb 15, 2018, at 8:45 AM, Daniel Ruggeri <DR...@primary.net> wrote:
>
> As mentioned before, I actually want to RM, but am still waiting for *any* confirmation that the dead-on-the-vine 2.6 release I bundled is at least structurally correct and matches project expectations. Since releases of source are one of the few things the version control time machine cannot undo (and are sacred things to the ASF as well), I want to be sure of the procedure. Maybe instead of doing the RM job, I could talk you into putting the (presumably less) volunteer time to vetting out the previous work so we can add to the number of folks willing and comfortable being RM?
>
> Side note, the slotmem fix seems like a showstopper, right? I'd want to see that in before a T&R.
> --
> Daniel Ruggeri
>
> On February 14, 2018 7:22:02 AM CST, Jim Jagielski <ji...@jaguNET.com> wrote:
>> I propose a T&R of 2.4.30 on Feb 19th. I offer to RM
>> unless someone else would like to do so.
Re: T&R of 2.4.30 Proposal
Posted by Daniel Ruggeri <dr...@primary.net>.
As mentioned before, I actually want to RM, but am still waiting for *any* confirmation that the dead-on-the-vine 2.6 release I bundled is at least structurally correct and matches project expectations. Since releases of source are one of the few things the version control time machine cannot undo (and are sacred things to the ASF as well), I want to be sure of the procedure. Maybe instead of doing the RM job, I could talk you into putting the (presumably less) volunteer time to vetting out the previous work so we can add to the number of folks willing and comfortable being RM?
Side note, the slotmem fix seems like a showstopper, right? I'd want to see that in before a T&R.
--
Daniel Ruggeri
On February 14, 2018 7:22:02 AM CST, Jim Jagielski <ji...@jaguNET.com> wrote:
>I propose a T&R of 2.4.30 on Feb 19th. I offer to RM
>unless someone else would like to do so.