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: local policy)
MIME-Version: 1.0
In-Reply-To: <43e40e001001051728l4fd0ed68r26a45b415ae161e6@mail.gmail.com>
References: <6f5b6fe71001041357g76b2b22fn93d083d22a08bf72@mail.gmail.com>
	 <yuatyv1uwei.fsf@slappy.mynet>
	 <89dd37e1001050318m1f72e89ak588bfe05eb0dd800@mail.gmail.com>
	 <89dd37e1001050611t1b314181hdae3d4d9eface86a@mail.gmail.com>
	 <43e40e001001051231n321cd09ewfd30dd62ae2a4970@mail.gmail.com>
	 <Pine.LNX.4.64.1001060857280.31037@ebfjryy.nhfvpf.arg>
	 <4B43CBAD.8030304@rowe-clan.net>
	 <43e40e001001051728l4fd0ed68r26a45b415ae161e6@mail.gmail.com>
Date: Wed, 6 Jan 2010 11:02:11 +0000
Message-ID: <6f5b6fe71001060302u4c64ced0s6fac1c85ccaa0764@mail.gmail.com>
Subject: Re: [VOTE] Formal deprecation of 1.3.x branch
From: =?ISO-8859-1?Q?Colm_MacC=E1rthaigh?= <colm@allcosts.net>
To: dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Based on this thread, I'll going to commit an EOL notice later today
(1.3.x is still CTR) and language nits and so on can be fixed with
patches/commits as appropriate, and if anyone feels strongly they can
revert :-)

On Wed, Jan 6, 2010 at 1:28 AM, Jorge Schrauwen
<jorge.schrauwen@gmail.com> wrote:
> On Wed, Jan 6, 2010 at 12:30 AM, William A. Rowe Jr.
> <wrowe@rowe-clan.net> wrote:
>> Res wrote:
>>> On Tue, 5 Jan 2010, Jorge Schrauwen wrote:
>>>
>>>> On Mon, Jan 4, 2010 at 11:03 PM, Rich Bowen <rbowen@rcbowen.com> wrote=
:
>>>>> Speaking from the community that provides end-user support for these
>>>>> products, a big +1 on that proposal.
>>>>>
>>>> Sadly, questions will keep on showing up for a long time :(
>>>
>>> I agree, however if it is EOL'd (yes Jeff, I agree this is likely more
>>> of an appropriate term :) ) you more or less can advise the requestor
>>> they are using a very old and unsupported version and that they should
>>> use the current stable version 2.2.xx
>>
>> These questions aren't a bother on an established 1.3 server, we all hav=
e
>> to support legacy systems.
>>
>> What is frightening is the number of users who are clearly deploying the=
ir
>> httpd server with 1.3, for the first time, and trying to learn that. =A0=
Almost
>> want to suggest to them that they go take a community college class on C=
OBOL
>> while they are at it, since they are clearly trying to improve their tec=
hnical
>> knowledge. =A0Heh
>>
>
> You could just put a anti troll like system where you ask a question
> only someone who's used 1.3 for a long time would know before letting
> them download. New users wouldn't be able to answer it and would be
> pointed to 2.2 branch ;)
> </sarc>
>
> It's understandable that you can't just magicly update a legacy 1.3 to
> a 2.x series without breaking a whole lot of stuff.
> But's sadly as you say, a lot users seem to be new to httpd and still
> grab 1.3 for some insane reason!
>
> Maybe adding some form of color coding (for the non-colorblind) on the
> download page, green -> current, orange/yellow -> old stable, red ->
> EOL
> Then again that would probably not have a big effect :(
>
> I also think punch cards > COBAL course! That will teach em to proof
> read there code before hitting compile ;)
>
> /me off to more studying
>
> Jorge
>


--=20
Colm