Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: message received from 54.191.145.13
 which is an MX secondary for dev@httpd.apache.org)
MIME-Version: 1.0
Date: Thu, 30 Apr 2015 16:52:47 -0500
Message-ID: 
 <CACsi250CPCr5khrVdk6+yp_oJzc=7H2nXatOV3jnxSKz_4jRwQ@mail.gmail.com>
Subject: Looking ahead to 2.4.13 / 2.2.30
From: William A Rowe Jr <wrowe@rowe-clan.net>
To: httpd <dev@httpd.apache.org>
Content-Type: multipart/alternative; boundary=90e6ba613b90ca7e010514f81d70

--90e6ba613b90ca7e010514f81d70
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 2, 2015 at 4:46 PM, William A. Rowe Jr. <wrowe@rowe-clan.net>
wrote:

> On Tue, 31 Mar 2015 10:49:47 -0400
> Jim Jagielski <jim@jaguNET.com> wrote:
>
> > BTW: Would it make sense to consider a release of 2.4.13 in April
> > to coincide w/ ApacheCon?
>
> We've historically produced a release at the beginning of the con.
> It worked really well when we would hackathon two days, then retire
> to do other con stuff for the balance of the event with a new
> release in the hopper looking for votes.
>
> I'd love to see us tag and roll releases based on our efforts
> throughout the entire gathering, sometime in that following week.
> I offer to T&R an update of 2.2 as well to pick up any issues we
> resolve over the course of that week.
>

It seems that we have 2 groups of good things to come out of ApacheCon,
some immediate fixes for things like BSD project efforts, some pretty
straightforward defects that have been resolved... and then there's a bunch
of energy about enhancements and the h2 universe.

In the short term, WDYT about giving the trees a week to settle, grab the
low hanging fruit and move forward for 2.4.13 and 2.2.30 end of this coming
week?  Guessing Jim's up for RM'ing 2.4.13, and I'm happy to T&R 2.2.30
in tandem.

Concerns / observations / thoughts?

Bill

--90e6ba613b90ca7e010514f81d70
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Apr 2, 2015 at 4:46 PM, William A. Rowe Jr. <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:wrowe@rowe-clan.net" target=3D"_blank">wrowe@rowe-clan.net</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, 31 Mar 2015 10=
:49:47 -0400<br>
Jim Jagielski &lt;jim@jaguNET.com&gt; wrote:<br>
<br>&gt; BTW: Would it make sense to consider a release of 2.4.13 in April<=
br>
&gt; to coincide w/ ApacheCon?<br>
<br>
We&#39;ve historically produced a release at the beginning of the con.<br>
It worked really well when we would hackathon two days, then retire<br>
to do other con stuff for the balance of the event with a new<br>
release in the hopper looking for votes.<br>
<br>
I&#39;d love to see us tag and roll releases based on our efforts<br>
throughout the entire gathering, sometime in that following week.<br>
I offer to T&amp;R an update of 2.2 as well to pick up any issues we<br>
resolve over the course of that week.<br></blockquote><div><br></div><div>I=
t seems that we have 2 groups of good things to come out of ApacheCon,</div=
><div>some immediate fixes for things like BSD project efforts, some pretty=
</div><div>straightforward defects that have been resolved... and then ther=
e&#39;s a bunch</div><div>of energy about enhancements and the h2 universe.=
</div><div><br></div><div>In the short term, WDYT about giving the trees a =
week to settle, grab the</div><div>low hanging fruit and move forward for 2=
.4.13 and 2.2.30 end of this coming</div><div>week?=C2=A0 Guessing Jim&#39;=
s up for RM&#39;ing 2.4.13, and I&#39;m happy to T&amp;R 2.2.30=C2=A0</div>=
<div>in tandem.</div><div><br></div><div>Concerns / observations / thoughts=
?</div><div><br></div><div>Bill</div></div></div></div>

--90e6ba613b90ca7e010514f81d70--