Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Date: Tue, 14 Dec 2004 11:10:48 -0500
From: Glenn Strauss <gs-apache-dev@gluelogic.com>
To: dev@httpd.apache.org
Subject: Re: [PATCH] fixing broken gnu ld (mis)detection problem
Message-ID: <20041214161048.GB28398@netspace.org>
References: <20041207204435.GA2449@nibiru.borg.metux.de>
 <20041207205307.GB2449@nibiru.borg.metux.de>
 <cc67648e04120805164cfba4bb@mail.gmail.com>
 <20041213042902.GB15811@nibiru.borg.metux.de>
 <41BD4682.8070109@force-elite.com>
 <20041213082040.GO15811@nibiru.borg.metux.de>
 <20041213140848.GB28041@quartz.newn.cam.ac.uk>
 <6.2.0.14.2.20041214031839.067f1670@pop3.rowe-clan.net>
 <20041214093336.GD22974@scotch.ics.uci.edu>
 <6.2.0.14.2.20041214035113.04c307b8@pop3.rowe-clan.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.2.0.14.2.20041214035113.04c307b8@pop3.rowe-clan.net>
User-Agent: Mutt/1.4.1i

On Tue, Dec 14, 2004 at 03:58:42AM -0600, William A. Rowe, Jr. wrote:
> I would like to see ALOT of feedback to current-testers or dev
> or even apache-modules of the alpha before declaring first beta.
> Once beta - we should be very adverse to API changes - our module
> authors will want to fix once and be done.  Or should we just
> trash the idea of alphas since not enough people are testing?
> Heck, while we are at it, lets just declare it GA.
> 
> The alpha better work for a good number of folks before we go
> to beta.  Then ya - as you say, the oddball kernel/distro issues
> will start popping up and be fixed pretty easily before GA.

A brief reminder of what Paul brought up, and I agree with:

Corporate project managers need a better sense of the release
schedule before they build test-time into their schedules.
I am not asking for hard-and-fast release dates, because httpd
is released when it is ready and not on artificial deadlines.

A completely open-ended release date -- as is currently the case --
is all but ignored by project managers.  Why spend time testing
something that is not going to be released for maybe another year
and will probably change immensely between now and then?

However, if releases were aimed for every, say, 6 months, with
a tag and semi-freeze two months prior, then I think we would see
a lot more testing by corporate users (who aren't already very
involved in this list) on those tags.

Cheers,
Glenn