Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Date: Mon, 15 Jan 2001 09:04:51 -0800 (PST)
From: dean gaudet <dgaudet-list-new-httpd@arctic.org>
To: <new-httpd@apache.org>
Subject: Re: Beta.
In-Reply-To: <Pine.LNX.4.21.0101111259060.18575-100000@koj>
Message-ID: <Pine.LNX.4.30.0101150902590.30402-100000@twinlark.arctic.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

does feature freeze mean no API changes to fix the problems i pointed out
with code that uses rprintf/rputs?  i'd be -1 on beta in that case.

i know there's been some responses from folks on that topic, but nothing
looks like anyone has a final answer.  i'm not convinced that the
performance problems can be solved given the current API.  as i mentioned
a long long time ago, this is an API i've worked with on another project,
and i ended up removing it to eliminate the performance problems that you
guys are now experiencing.

-dean

On Thu, 11 Jan 2001 rbb@covalent.net wrote:

>
> I am sick of Apache 2.0.  That doesn't mean that I am ready to stop
> working on it, I'm not.  I love this piece of software, and I am likely to
> be working on Apache 2.0 for it's full life cycle.  It does mean that I am
> ready to move from Apache 2.0 alpha to Apache 2.0 beta to Apache 2.0.
>
> I believe that this means that we have to make a concerted effort to get
> this release to a beta version soon.  I would like to ask that we go into
> feature freeze now.  This means we will fix bugs, but that is it until we
> hit beta.
>
> Now, if after we hit beta, we want to add new features, that is a decision
> we can make.  Personally, I don't believe we should.  The Apache group
> entered a feature freeze before Apache 1.2 and 1.3.  This is obvious by
> looking at the bug reports that were suspended with the message:  "We are
> too far into this development cycle to add a new feature, we will
> reconsider for X.X".
>
> When I say fix bugs, by the way, I consider anything in the STATUS
> file right now a bug.  I do not believe we should add everything to the
> STATUS file tonight.  If it isn't already in the STATUS file, it isn't a
> known bug.  We may find more bugs, but that is very different from saying
> that there is a new feature we want to add, so it is now a bug.
>
> Thoughts, comments?
>
> Ryan
>
>
> _______________________________________________________________________________
> Ryan Bloom                        	rbb@apache.org
> 406 29th St.
> San Francisco, CA 94131
> -------------------------------------------------------------------------------
>
>
>
>
>
>