Received: by taz.hyperreal.com (8.8.3/V2.0) id VAA27869; Thu, 5 Dec 1996 21:40:13 -0800 (PST) Received: from plato.alameda-coe.k12.ca.us by taz.hyperreal.com (8.8.3/V2.0) with SMTP id VAA27865; Thu, 5 Dec 1996 21:40:08 -0800 (PST) Received: from pappilloma.wwebsvs.com by plato.alameda-coe.k12.ca.us with smtp (Smail3.1.29.1 #5) id m0vVsur-000OarC; Thu, 5 Dec 96 21:33 PST Received: from ace.nueva.pvt.k12.ca.us by pappilloma.wwebsvs.com (SMI-8.6/SMI-SVR4) id UAA00806; Thu, 5 Dec 1996 20:38:58 -0800 Received: from localhost by ace.nueva.pvt.k12.ca.us with SMTP (1.37.109.20/15.5+ECS 3.3+HPL1.1) id AA246260781; Thu, 5 Dec 1996 21:39:41 -0800 Date: Thu, 5 Dec 1996 21:39:40 -0800 (PST) From: Alexei Kosut To: new-httpd@hyperreal.com Subject: Re: 1.2 final timetable In-Reply-To: <199612060348.DAA09100> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com On Fri, 6 Dec 1996, Rob Hartill wrote: > Do we have a timetable for a 1.2 final release ? > > I mentioned Jan 1st a while back. Ben showed an interest in keeping > us on track as a release manager for that. Now that 1.2b is out there, > we've picked up some momentum and a Jan 1st release date looks > comfortable, even with the xmas holiday period, so we probably won't > need to be dragged kicking and screaming to get there. Sounds good to me, assuming no major problems show up. > A more formal plan/timetable for 2.0 will be very important though. IMO. > Does anyone have their eye on the manager's job for 2.0 ? I don't think we need a timetable yet - at least not for a release. We do, however, need a plan on how to start. The idea, as of last July, was to start with RST's threaded version of Apache. I don't recall seeing Rob post any messages here in a while, so I don't know what the current status of that it. If that would still be the idea, we'd have to update with all the 1.2.0 status (assuming RST hasn't done that already), then plug it into the CVS tree and let people play with it. We also need to incorporate other things. An NT port, for example, would need to be worked out and incorporated. If we wanted to reformat the code, that's something that needs to be scheduled and done (hopefully) in a well-fashioned manner. For the rest, though, I think we can just go for a "let's take six months and do stuff to Apache" approach. I'd manage 2.0, if no one else wants to. -- ________________________________________________________________________ Alexei Kosut The Apache HTTP Server URL: http://www.nueva.pvt.k12.ca.us/~akosut/ http://www.apache.org/