Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 38381 invoked by uid 500); 9 Oct 2000 21:33:40 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 38370 invoked from network); 9 Oct 2000 21:33:39 -0000 From: mja@trudge.engr.sgi.com (Mike Abbott) Message-Id: <200010092132.OAA67128@trudge.engr.sgi.com> Subject: Re: Plan for 2.0b1 To: new-httpd@apache.org Date: Mon, 9 Oct 2000 14:32:42 -0700 (PDT) In-Reply-To: from "rbb@covalent.net" at Oct 09, 2000 08:41:35 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > The list: > Remove Buff from the server completely > Fix mod_include > Cleanup some memory leaks > Search for and fix all the XXX's in the code The beta should also fix all open bugs against all 2.0 alphas, merge in all changes made only to 1.3 since the split, and include comprehensive documentation on the new API and features. Personally, I'd keep rolling alphas until an alpha that has been out for a while is stable enough to be promoted to beta as-is, rather than foist a brand new snapshot on the world as a beta. But, that's just me. -- Michael J. Abbott mja@sgi.com http://reality.sgi.com/mja/