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: domain of trawick@gmail.com designates
 209.85.128.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <20130620150701.51f6c1c6@hub>
References: <20130620150701.51f6c1c6@hub>
Date: Thu, 20 Jun 2013 16:48:08 -0400
Message-ID: 
 <CAKUrXK7BGVcHWDycict37cxN7pXkFD7EN+4=Cr4uNgE1bEsYow@mail.gmail.com>
Subject: Re: T-24:00:00 to 2.0, 2.2 final tags
From: Jeff Trawick <trawick@gmail.com>
To: Apache HTTP Server Development List <dev@httpd.apache.org>
Content-Type: multipart/alternative; boundary=bcaec50166b556fc6204df9c103c

--bcaec50166b556fc6204df9c103c
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jun 20, 2013 at 4:07 PM, William A. Rowe Jr. <wrowe@rowe-clan.net>wrote:

> Devs,
>
> I plan to tag both the 2.0 and 2.2 trees now that they look relatively
> stable, given that we are a couple weeks beyond the originally discussed
> 2.0/2.2/2.4 simultaneous release.  There is one backport to apply in 2.2
> and we had been waiting for Jeff to confirm that the proposed security
> fix now addresses all of his issues now in the 2.0 tree.


Ouch!  I do remember rjung (?) leaving a note in STATUS (?) but I had
scrolling inbox+disorganization syndrome.  I'll play with that now.  Sorry!


>  I have free
> time to do this tomorrow late afternoon, so if anyone has their fingers
> in the trees with last minute work, send me a heads up so I can avoid
> colliding with your efforts.
>
> If there is a 2.4 vote proceeding smoothly we can always defer the
> announce so that there is a single, clear message we recommend 2.4,
> that 2.2 is a maintenance release for legacy users, and that 2.0
> represents the final release of that software and that it will no
> longer be maintained by the project.
>


-- 
Born in Roswell... married an alien...
http://emptyhammock.com/

--bcaec50166b556fc6204df9c103c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Jun 20, 2013 at 4:07 PM, William A. Rowe Jr. <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:wrowe@rowe-clan.net" target=3D"_blank">w=
rowe@rowe-clan.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div=
 class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Devs,<br>
<br>
I plan to tag both the 2.0 and 2.2 trees now that they look relatively<br>
stable, given that we are a couple weeks beyond the originally discussed<br=
>
2.0/2.2/2.4 simultaneous release. =A0There is one backport to apply in 2.2<=
br>
and we had been waiting for Jeff to confirm that the proposed security<br>
fix now addresses all of his issues now in the 2.0 tree.</blockquote><div><=
br></div><div style>Ouch! =A0I do remember rjung (?) leaving a note in STAT=
US (?) but I had scrolling inbox+disorganization syndrome. =A0I&#39;ll play=
 with that now. =A0Sorry!</div>
<div style><br></div><div style>=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> =
=A0I have free<br>
time to do this tomorrow late afternoon, so if anyone has their fingers<br>
in the trees with last minute work, send me a heads up so I can avoid<br>
colliding with your efforts.<br>
<br>
If there is a 2.4 vote proceeding smoothly we can always defer the<br>
announce so that there is a single, clear message we recommend 2.4,<br>
that 2.2 is a maintenance release for legacy users, and that 2.0<br>
represents the final release of that software and that it will no<br>
longer be maintained by the project.<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Born in Rosw=
ell... married an alien...<br><a href=3D"http://emptyhammock.com/" target=
=3D"_blank">http://emptyhammock.com/</a><br>
</div></div>

--bcaec50166b556fc6204df9c103c--