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 info@apachelounge.com
 designates 85.223.52.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=default; d=apachelounge.com;
	h=Subject:From:Date;
	b=kLVGoBJc+kDKj+BmXJaq+zvskJUu0qVkUPY+D2VXkqJQlnlpSlZhUGEbN3lNmixIO8cXk8J0HCl3vs1v4Lq6dMq7PKnhgZq5Agf619oFfEuiT4K4MTcUtih1FRwMFVDn;
Subject: Re: ******* Re: Time for 2.4.0 GA??
References: <8098B085-D1EB-4461-8BD4-9DEFE3D1697A@jaguNET.com>
 <58690B38-A116-47F5-9BC9-FAA8FE693CB0@apachelounge.com>
 <1F711E32-E28E-4CB4-84E6-834D6CE5E51A@apache.org>
 <24B1479E-5714-443D-86EC-962A9350F40B@apachelounge.com>
 <6FC832C4-454D-47BA-970B-B32AC1C68761@sharp.fm>
From: Steffen <info@apachelounge.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <6FC832C4-454D-47BA-970B-B32AC1C68761@sharp.fm>
Message-Id: <6F572370-958F-4B06-9751-504701E542DF@apachelounge.com>
Date: Mon, 16 Jan 2012 14:34:31 +0000
To: "dev@httpd.apache.org" <dev@httpd.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

Unbelievable this answer, I am stimulating users to use it and with success.=
 I feel, you are accusing me here and the windows community. No problem, we a=
re continuing to let you know what issues we discover. In principal up to yo=
u how you handle issues  Keep in mind we are just users, no dev's.=20

When you and other dev's should participate at  AL, should be good for the t=
wo worlds.=20

So no way that the ASF would run a windows site, pity.=20

For example I think Mario described the balancer issue quite good, but see n=
o attention for a long time. More examples if you want. The former ipv6 issu=
es is the winner, years before some give attention, even we (sob) supplied a=
 fix. Also mod_fcgid has a fix provided by Mario, also not picked up. AL is p=
roviding a mod_fcgid binary with three fixes, so at some point we can solve t=
hings by ourselves.=20

I already agreed to 2.4 GA, why wait so long. Not me is delaying.=20

2.3 is already in hands/running of at least a few thousands  users for quite=
 some time.  Based on the number of downloads and the good/bad reports we ge=
t.  Special the PHP community is a big downloader and use.   Enough to see h=
ow 2.4 should  go. I think 2.3 is great, some has bad luck with eg.  no ssl u=
sable.=20

To run 2.3 without SSL issues, 2.2 in front(proxy) overcomes it. So no hurry=
 to solve the issue.=20

Steffen

Op 16 jan. 2012 om 13:07 heeft Graham Leggett <minfrin@sharp.fm> het volgend=
e geschreven:

> On 16 Jan 2012, at 2:31 PM, Steffen wrote:
>=20
>> Thanks for the understanding.=20
>>=20
>> Experience is that win issues hardly land in the status. Mostly the answe=
r is make a bug report, and it is of the table and sitting as reported bug f=
or a very long time. Take for example the serious bug from Mario about the b=
alancer in 2.3. An other are the mod_fcgid bugs.=20
>>=20
>> Also I cannot believe  that eg the rewrite p issue was/is(?) only win.=20=

>>=20
>> I propose that the ASF is also going to run windows on one of the heavier=
/complex  sites !!  Maybe a vote on that can started.  Please consider.=20
>=20
> The best way to find and fix the Windows bugs is to get the code into the h=
ands of the Windows users, and to do that we must release v2.4.0 as soon as p=
ossible.
>=20
> Trying to delay the release indefinitely until an arbitrary list of bugs i=
s fixed is counterproductive - you're just keeping the code out of the hands=
 of those who are able to either describe the problem in enough detail that i=
t can be reproduced, or those who could potentially fix the problem and subm=
it the fix to us.
>=20
> The "dot zero" in "2.4.0" is well understood.
>=20
> Regards,
> Graham
> --
>=20