Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of jblond@gmail.com designates
 209.85.212.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F02B91D.4050300@gknw.net>
References: <201201022310.40139.sf@sfritsch.de>
	<4F023883.2080901@rowe-clan.net>
	<4F02B91D.4050300@gknw.net>
Date: Tue, 3 Jan 2012 10:26:58 +0100
Message-ID: 
 <CAA=k7mWU3Vc8YpRxYiOG1MMbMwrD9b+vtzX6gF=5jYo6MAKpNg@mail.gmail.com>
Subject: Re: 2.4.0 GA This week?
From: Mario Brandt <jblond@gmail.com>
To: dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I agree with Gregg, this server is the best I ever worked with. Since
one of the early betas I run it on my prod systems on windows and
*nix. Except for known issues it works like a charm.
A public beta or RC does not hurt. More testers may find some more
stuff to fix. An api freeze coulod gve the 3rd party module guys give
the time to fix and or build
their modules against coming 2.4

Go the way on releasing it for one system as GA and others as beta is
confusing in my eyes.

Just my 2 cents
Mario

> I all for stop any and all API changes other than anything that may requi=
re
> fixing these.
> I am all for RCs if it means changing the -dev is to -rc#
>
> I'm sorry I signed off before I realized SSL with =A0"AcceptFilter httpd =
none"
> =A0was still a problem on Windoze.
> Yes, Mario's mod_proxy_balancer/slotmem shm errors I am also still gettin=
g/
> Mario, I know you read this list ... chime in your PR#
>
> and any other possitivle showstopper that may be on any platform other th=
an
> building =A0... not that I count :)
>
> Other than these few ... bummers ... guys ... this is one of the best
> servers I have seen.
>
> Cheets
>
> Gregg
>