You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "William A. Rowe Jr." <wr...@rowe-clan.net> on 2011/11/11 17:49:28 UTC

[VOTE] Formal deprecation of 2.0.x branch

Stealing a plan executed by Colm for 1.3, I'd like to propose that
we set a two week window following committers' return-from-ApacheCon
to execute any backports "of general interest" and apply important
fixes/backports to pregsub allocation and non-absolute uri parsing.

On approval of this plan, I would offer to introduce the EOL notices
(as we ultimately committed to 1.3), tag and roll 2.0.65 on Nov 26th
and we would potentially approve and release 2.0 'final' this month.

And as we did with 1.3, we would start a 12 month clock to removing
2.0.x pretty much in its entirety from the live httpd.apache.org site
and /dist/ mirrors (although still available from archive.a.o/dist/).

Otherwise we will be developing towards 4 releases even beyond this
month, which seems excessive when the current stable has rendered
the prior version obsolete six years ago, on December 1, 2005.


Re: [Discuss] [VOTE] Formal deprecation of 2.0.x branch

Posted by Noel Butler <no...@ausics.net>.
On Fri, 2011-11-11 at 14:25 -0600, William A. Rowe Jr. wrote:

> On 11/11/2011 1:42 PM, Issac Goldstand wrote:
> > -0
> >
> > I DO want the EOL, but not until after 2.4 has a couple of GAs, if only
> > because folks might not update twice.
> 
> They've had six years?  I'm talking deprecating 2.0, not 2.2,
> for 2.4 -or- 2.2.  Lots of choices, including putting off any
> upgrade.
> 
> They have as long as they like to update.  The 2.0.65 would not
> suddenly stop functioning.  But if it doesn't work as they
> desire, they need to pick 2.2.x or 2.4.x, and there won't be
> some 2.0.66 at some arbitrary date a year or so out (as the
> past couple releases have been spaced apart).
> 
> This action sets up one clear signal, there will not be another
> 2.0.x to follow, so don't wait around for one, look to the 2.4
> and 2.2 stable releases if you want something the project will
> keep updating, no matter how infrequently in the case of 2.2.
> 
> Bill


Agreed, EOL of  2.0 is  _long_ overdue



[Discuss] [VOTE] Formal deprecation of 2.0.x branch

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 11/11/2011 1:42 PM, Issac Goldstand wrote:
> -0
>
> I DO want the EOL, but not until after 2.4 has a couple of GAs, if only
> because folks might not update twice.

They've had six years?  I'm talking deprecating 2.0, not 2.2,
for 2.4 -or- 2.2.  Lots of choices, including putting off any
upgrade.

They have as long as they like to update.  The 2.0.65 would not
suddenly stop functioning.  But if it doesn't work as they
desire, they need to pick 2.2.x or 2.4.x, and there won't be
some 2.0.66 at some arbitrary date a year or so out (as the
past couple releases have been spaced apart).

This action sets up one clear signal, there will not be another
2.0.x to follow, so don't wait around for one, look to the 2.4
and 2.2 stable releases if you want something the project will
keep updating, no matter how infrequently in the case of 2.2.

Bill

Re: [VOTE] Formal deprecation of 2.0.x branch

Posted by Issac Goldstand <ma...@beamartyr.net>.
-0

I DO want the EOL, but not until after 2.4 has a couple of GAs, if only
because folks might not update twice.

  Issac

On 11/11/2011 09:13, "Plüm, Rüdiger, VF-Group" wrote:
> +1 
>
> Regards
>
> Rüdiger
>
>> -----Original Message-----
>> From: William A. Rowe Jr. 
>> Sent: Freitag, 11. November 2011 17:49
>> To: dev@httpd.apache.org
>> Subject: [VOTE] Formal deprecation of 2.0.x branch
>>
>> Stealing a plan executed by Colm for 1.3, I'd like to propose that
>> we set a two week window following committers' return-from-ApacheCon
>> to execute any backports "of general interest" and apply important
>> fixes/backports to pregsub allocation and non-absolute uri parsing.
>>
>> On approval of this plan, I would offer to introduce the EOL notices
>> (as we ultimately committed to 1.3), tag and roll 2.0.65 on Nov 26th
>> and we would potentially approve and release 2.0 'final' this month.
>>
>> And as we did with 1.3, we would start a 12 month clock to removing
>> 2.0.x pretty much in its entirety from the live httpd.apache.org site
>> and /dist/ mirrors (although still available from archive.a.o/dist/).
>>
>> Otherwise we will be developing towards 4 releases even beyond this
>> month, which seems excessive when the current stable has rendered
>> the prior version obsolete six years ago, on December 1, 2005.
>>
>>


RE: [VOTE] Formal deprecation of 2.0.x branch

Posted by "Plüm, Rüdiger, VF-Group" <ru...@vodafone.com>.
+1 

Regards

Rüdiger

> -----Original Message-----
> From: William A. Rowe Jr. 
> Sent: Freitag, 11. November 2011 17:49
> To: dev@httpd.apache.org
> Subject: [VOTE] Formal deprecation of 2.0.x branch
> 
> Stealing a plan executed by Colm for 1.3, I'd like to propose that
> we set a two week window following committers' return-from-ApacheCon
> to execute any backports "of general interest" and apply important
> fixes/backports to pregsub allocation and non-absolute uri parsing.
> 
> On approval of this plan, I would offer to introduce the EOL notices
> (as we ultimately committed to 1.3), tag and roll 2.0.65 on Nov 26th
> and we would potentially approve and release 2.0 'final' this month.
> 
> And as we did with 1.3, we would start a 12 month clock to removing
> 2.0.x pretty much in its entirety from the live httpd.apache.org site
> and /dist/ mirrors (although still available from archive.a.o/dist/).
> 
> Otherwise we will be developing towards 4 releases even beyond this
> month, which seems excessive when the current stable has rendered
> the prior version obsolete six years ago, on December 1, 2005.
> 
> 

Re: [Discuss] [VOTE] Formal deprecation of 2.0.x branch

Posted by Stefan Fritsch <sf...@sfritsch.de>.
On Fri, 11 Nov 2011, Rainer Jung wrote:
>> I wouldn't call that "final", since, well it obviously isn't.
>> 
>> We should send a clear message here, simply saying:
>> 
>> - no more features
>> - no more bugfixes, except security related ones
>> - no more anything after, e.g., 31.12.2012
>> 
>> And we should mean it. If that's the plan, fine.
>
> I like this formulation. BTW: we discussed this about two months ago already:

+1

>
> http://marc.info/?t=131615234300003&r=1&w=2
>
> Mostly the same result, except that the EOL was said to be GA for 2.4.0 plus 
> 12 months. But the difference to 21.12.2012 doesn't matter.
>
> Regards,
>
> Rainer
>

Re: [Discuss] [VOTE] Formal deprecation of 2.0.x branch

Posted by Rainer Jung <ra...@kippdata.de>.
On 11.11.2011 13:04, André Malo wrote:
> * William A. Rowe Jr. wrote:
>
>> So isn't it enough to say that "The project will choose to publish
>> further releases only for significant security fixes, or will choose
>> instead to publish patches for less significant security fixes for
>> 12 months from the date of this final release.  From December 2012,
>> no further security patches or releases should be expected for the
>> 2.0.x release family."?
>>
>> More useful here to tweak the message than the plan, no?
>
> I wouldn't call that "final", since, well it obviously isn't.
>
> We should send a clear message here, simply saying:
>
> - no more features
> - no more bugfixes, except security related ones
> - no more anything after, e.g., 31.12.2012
>
> And we should mean it. If that's the plan, fine.

I like this formulation. BTW: we discussed this about two months ago 
already:

http://marc.info/?t=131615234300003&r=1&w=2

Mostly the same result, except that the EOL was said to be GA for 2.4.0 
plus 12 months. But the difference to 21.12.2012 doesn't matter.

Regards,

Rainer

Re: [Discuss] [VOTE] Formal deprecation of 2.0.x branch

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 11/11/2011 3:04 PM, André Malo wrote:
> * William A. Rowe Jr. wrote:
>
>> So isn't it enough to say that "The project will choose to publish
>> further releases only for significant security fixes, or will choose
>> instead to publish patches for less significant security fixes for
>> 12 months from the date of this final release.  From December 2012,
>> no further security patches or releases should be expected for the
>> 2.0.x release family."?
>>
>> More useful here to tweak the message than the plan, no?
>
> I wouldn't call that "final", since, well it obviously isn't.

"Final Scheduled Maintenance Release"?  [Yes, it won't necessarily
be the final Security release, and I appreciate the humor that we
don't have a release calendar.  Better wording that retains the
word Final?]]


Re: [Discuss] [VOTE] Formal deprecation of 2.0.x branch

Posted by André Malo <nd...@perlig.de>.
* William A. Rowe Jr. wrote:

> So isn't it enough to say that "The project will choose to publish
> further releases only for significant security fixes, or will choose
> instead to publish patches for less significant security fixes for
> 12 months from the date of this final release.  From December 2012,
> no further security patches or releases should be expected for the
> 2.0.x release family."?
>
> More useful here to tweak the message than the plan, no?

I wouldn't call that "final", since, well it obviously isn't.

We should send a clear message here, simply saying:

- no more features
- no more bugfixes, except security related ones
- no more anything after, e.g., 31.12.2012

And we should mean it. If that's the plan, fine.

(I find your wording not that clear, but that may be a language issue on my 
side.)

nd
-- 
"Eine Eieruhr", erklärt ihr Hermann, "besteht aus einem Ei. Du nimmst
das Ei und kochst es. Wenn es hart ist, sind fünf Minuten um. Dann weißt
du, daß die Zeit vergangen ist."
                             -- Hannes Hüttner in "Das Blaue vom Himmel"

Re: [Discuss] [VOTE] Formal deprecation of 2.0.x branch

Posted by Jeff Trawick <tr...@gmail.com>.
On Sat, Nov 12, 2011 at 3:38 PM, Noel Butler <no...@ausics.net> wrote:
> On Sat, 2011-11-12 at 07:00 -0600, William A. Rowe Jr. wrote:
>
> On 11/11/2011 3:12 PM, Paul Querna wrote:
>>
>> I don't see why we would continue to support 2.0.x for longer than
>> Redhat's already long support cycles.
>
> I don't see why we would tie this to RedHat's schedule or any other
> vendor, including my own.
>
>
> +1
> Apache (like most daemons), move forward, it's tuff luck if certain distros
> (which RedHat is not the only popular one), that insists on continuing to
> live in the dark ages.

Businesses are generally happy to pay to keep certain environments in
the (mostly) dark ages.  Whether for proprietary software or
vendor-supported open source, there's a lot of value in using a stable
stack which is changed only for critical fixes, in order to avoid
dealing with behavior changes, the inevitable regressions that come
from wide open releases/branches, etc..  Businesses want to put most
of their efforts into new projects (which will use current stacks) and
minimize excitement (and resulting efforts) on old projects that
aren't yet slated for replacement or at least bringing up to
&currentYear.

When we put a branch out to pasture the obvious positive is the strong
message to those with leeway to invest in an upgrade and retest
("recertification") their applications but a drawback is the
disappearance of a place to share efforts among those who still must
maintain the branch, whether for their [employer's] own projects or
for their customers.

Re: [Discuss] [VOTE] Formal deprecation of 2.0.x branch

Posted by Noel Butler <no...@ausics.net>.
On Sat, 2011-11-12 at 07:00 -0600, William A. Rowe Jr. wrote:

> On 11/11/2011 3:12 PM, Paul Querna wrote:
> >
> > I don't see why we would continue to support 2.0.x for longer than
> > Redhat's already long support cycles.
> 
> I don't see why we would tie this to RedHat's schedule or any other
> vendor, including my own.
> 


+1 
Apache (like most daemons), move forward, it's tuff luck if certain
distros (which RedHat is not the only popular one), that insists on
continuing to live in the dark ages.

(and if they are using something that old Apache is likely the least of
their problems)



Re: [Discuss] [VOTE] Formal deprecation of 2.0.x branch

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 11/12/2011 7:00 AM, William A. Rowe Jr. wrote:
> On 11/11/2011 3:12 PM, Paul Querna wrote:
>>
>> I don't see why we would continue to support 2.0.x for longer than
>> Redhat's already long support cycles.
>
> I don't see why we would tie this to RedHat's schedule or any other
> vendor, including my own.

To reiterate, I'm not picking on RedHat or VMware or Oracle or any
other distributor, free or commercial ;-)  It was just one name
example that Paul happened to suggest... hope nobody took offense.


Re: [Discuss] [VOTE] Formal deprecation of 2.0.x branch

Posted by Mads Toftum <ma...@toftum.dk>.
On Sat, Nov 12, 2011 at 07:00:07AM -0600, William A. Rowe Jr. wrote:
> On 11/11/2011 3:12 PM, Paul Querna wrote:
> >
> >I don't see why we would continue to support 2.0.x for longer than
> >Redhat's already long support cycles.
> 
> I don't see why we would tie this to RedHat's schedule or any other
> vendor, including my own.

If you did, then perhaps Solaris 10 was another option - that's around
for at least another 5 years with 2.0. :)

vh

Mads Toftum
-- 
http://soulfood.dk

Re: [Discuss] [VOTE] Formal deprecation of 2.0.x branch

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 11/11/2011 3:12 PM, Paul Querna wrote:
>
> I don't see why we would continue to support 2.0.x for longer than
> Redhat's already long support cycles.

I don't see why we would tie this to RedHat's schedule or any other
vendor, including my own.


Re: [Discuss] [VOTE] Formal deprecation of 2.0.x branch

Posted by Paul Querna <pa...@querna.org>.
On Fri, Nov 11, 2011 at 12:34 PM, William A. Rowe Jr.
<wr...@rowe-clan.net> wrote:
> On 11/11/2011 1:47 PM, André Malo wrote:
>>
>> * William A. Rowe Jr. wrote:
>>
>>> Stealing a plan executed by Colm for 1.3, I'd like to propose that
>>> we set a two week window following committers' return-from-ApacheCon
>>> to execute any backports "of general interest" and apply important
>>> fixes/backports to pregsub allocation and non-absolute uri parsing.
>>>
>>> On approval of this plan, I would offer to introduce the EOL notices
>>> (as we ultimately committed to 1.3), tag and roll 2.0.65 on Nov 26th
>>> and we would potentially approve and release 2.0 'final' this month.
>>
>> I'd prefer a "security only from now on" announcement / warning first, and
>> keep it that way about another year or so. I don't think the users of 2.0
>> are actually prepared for a statement like "support is gone now, effective
>> immediately".
>>
>> We can put a statement into the docs similar to 1.3 (this time
>> automated...)
>
> So isn't it enough to say that "The project will choose to publish
> further releases only for significant security fixes, or will choose
> instead to publish patches for less significant security fixes for
> 12 months from the date of this final release.  From December 2012,
> no further security patches or releases should be expected for the
> 2.0.x release family."?
>
> More useful here to tweak the message than the plan, no?


https://access.redhat.com/support/policy/updates/errata/

RHEL 4 EOLs production support February 29, 2012.

RHEL 4 includes 2.0.52.

RHEL 5 includes 2.2.x

I don't see why we would continue to support 2.0.x for longer than
Redhat's already long support cycles.

[Discuss] [VOTE] Formal deprecation of 2.0.x branch

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 11/11/2011 1:47 PM, André Malo wrote:
> * William A. Rowe Jr. wrote:
>
>> Stealing a plan executed by Colm for 1.3, I'd like to propose that
>> we set a two week window following committers' return-from-ApacheCon
>> to execute any backports "of general interest" and apply important
>> fixes/backports to pregsub allocation and non-absolute uri parsing.
>>
>> On approval of this plan, I would offer to introduce the EOL notices
>> (as we ultimately committed to 1.3), tag and roll 2.0.65 on Nov 26th
>> and we would potentially approve and release 2.0 'final' this month.
>
> I'd prefer a "security only from now on" announcement / warning first, and
> keep it that way about another year or so. I don't think the users of 2.0
> are actually prepared for a statement like "support is gone now, effective
> immediately".
>
> We can put a statement into the docs similar to 1.3 (this time automated...)

So isn't it enough to say that "The project will choose to publish
further releases only for significant security fixes, or will choose
instead to publish patches for less significant security fixes for
12 months from the date of this final release.  From December 2012,
no further security patches or releases should be expected for the
2.0.x release family."?

More useful here to tweak the message than the plan, no?


Re: [VOTE] Formal deprecation of 2.0.x branch

Posted by André Malo <nd...@perlig.de>.
* William A. Rowe Jr. wrote:

> Stealing a plan executed by Colm for 1.3, I'd like to propose that
> we set a two week window following committers' return-from-ApacheCon
> to execute any backports "of general interest" and apply important
> fixes/backports to pregsub allocation and non-absolute uri parsing.
>
> On approval of this plan, I would offer to introduce the EOL notices
> (as we ultimately committed to 1.3), tag and roll 2.0.65 on Nov 26th
> and we would potentially approve and release 2.0 'final' this month.

I'd prefer a "security only from now on" announcement / warning first, and 
keep it that way about another year or so. I don't think the users of 2.0 
are actually prepared for a statement like "support is gone now, effective 
immediately".

We can put a statement into the docs similar to 1.3 (this time automated...)

.02€

However, since this is supposed to be a vote thread: -1 for "final".

nd
-- 
Real programmers confuse Christmas and Halloween because
DEC 25 = OCT 31.  -- Unknown

                                      (found in ssl_engine_mutex.c)

Re: [VOTE] Formal deprecation of 2.0.x branch

Posted by Sander Temme <sc...@apache.org>.
On Nov 11, 2011, at 8:49 AM, William A. Rowe Jr. wrote:

> Stealing a plan executed by Colm for 1.3, I'd like to propose that
> we set a two week window following committers' return-from-ApacheCon
> to execute any backports "of general interest" and apply important
> fixes/backports to pregsub allocation and non-absolute uri parsing.
> 
> On approval of this plan, I would offer to introduce the EOL notices
> (as we ultimately committed to 1.3), tag and roll 2.0.65 on Nov 26th
> and we would potentially approve and release 2.0 'final' this month.
> 
> And as we did with 1.3, we would start a 12 month clock to removing
> 2.0.x pretty much in its entirety from the live httpd.apache.org site
> and /dist/ mirrors (although still available from archive.a.o/dist/).
> 
> Otherwise we will be developing towards 4 releases even beyond this
> month, which seems excessive when the current stable has rendered
> the prior version obsolete six years ago, on December 1, 2005.

+1.  It is time.

S.

-- 
sctemme@apache.org            http://www.temme.net/sander/
PGP FP: FC5A 6FC6 2E25 2DFD 8007  EE23 9BB8 63B0 F51B B88A

View my availability: http://tungle.me/sctemme



Re: [VOTE] Formal deprecation of 2.0.x branch

Posted by jean-frederic clere <jf...@gmail.com>.
+1

Cheers

Jean-Frederic

Re: [VOTE] Formal deprecation of 2.0.x branch

Posted by Daniel Ruggeri <DR...@primary.net>.
On 11/11/2011 10:49 AM, William A. Rowe Jr. wrote:
> And as we did with 1.3, we would start a 12 month clock to removing
> 2.0.x pretty much in its entirety from the live httpd.apache.org site
> and /dist/ mirrors (although still available from archive.a.o/dist/). 

+1. It's time to say goodbye.

-- 
Daniel Ruggeri


Re: [VOTE] Formal deprecation of 2.0.x branch

Posted by Igor Galić <i....@brainsware.org>.

----- Original Message -----
> On Fri, Nov 11, 2011 at 11:49 AM, William A. Rowe Jr.
> <wr...@rowe-clan.net> wrote:
> > Stealing a plan executed by Colm for 1.3, I'd like to propose that
> > we set a two week window following committers'
> > return-from-ApacheCon
> > to execute any backports "of general interest" and apply important
> > fixes/backports to pregsub allocation and non-absolute uri parsing.
> >

+1

i

-- 
Igor Galić

Tel: +43 (0) 664 886 22 883
Mail: i.galic@brainsware.org
URL: http://brainsware.org/
GPG: 6880 4155 74BD FD7C B515  2EA5 4B1D 9E08 A097 C9AE


Re: [VOTE] Formal deprecation of 2.0.x branch

Posted by Eric Covener <co...@gmail.com>.
On Fri, Nov 11, 2011 at 11:49 AM, William A. Rowe Jr.
<wr...@rowe-clan.net> wrote:
> Stealing a plan executed by Colm for 1.3, I'd like to propose that
> we set a two week window following committers' return-from-ApacheCon
> to execute any backports "of general interest" and apply important
> fixes/backports to pregsub allocation and non-absolute uri parsing.
>

+1

2.0.65 countdown

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 11/11/2011 10:49 AM, William A. Rowe Jr. wrote:
>
> On approval of this plan, I would offer to introduce the EOL notices
> (as we ultimately committed to 1.3), tag and roll 2.0.65 on Nov 26th
> and we would potentially approve and release 2.0 'final' this month.

I have responded to all negative comments with small language tweaks
which would help clarify that this is the last maintenance release,
although we would reserve the right to push out a security release.
With 2.4 "immanent", we aught to lighten our burden and direct our
users to the best software available.

I've seen a number of positive votes on this plan.  However, Nov 26th
is now coming up in a week.  This is just a gentle prod to consider
proposing backports over this weekend into early next week.  You
may not find a lot of help from US committers beyond Wednesday due to
madness which ensues in the US over that weekend.