Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 88667 invoked by uid 500); 2 May 2002 18:25:50 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 88652 invoked from network); 2 May 2002 18:25:50 -0000 User-Agent: Microsoft-Entourage/10.0.0.1331 Date: Thu, 02 May 2002 19:25:48 +0100 Subject: Re: Final bump and roll of 2.0.36 From: Pier Fumagalli To: Message-ID: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N "Sander Striker" wrote: >>> What about GA? >> >> IMO: >> >> pros: >> * we do people more of a disservice by continue to have them use 2.0.35 >> and find already fixed bugs than by throwing another release at them >> three weeks later >> * what you said >> >> cons: >> * worker shutdown is still wonky, at least on linux. part of me would >> have rather seen it segfault. but just stick a warning in the release >> notes to be wary of the potential rough edges there, and I'm okay with >> it > > +1. Lets give it the rest of the week and the weekend. Start moving for > announce of GA on monday. Nagoya is running 2.0.36 with worker, ATM, so if you want to give it a blast, don't worry... In theory nothing should go bad, right? :) :) :) Pier