Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 31860 invoked by uid 500); 20 Jul 2001 19:02:22 -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 31841 invoked from network); 20 Jul 2001 19:02:22 -0000 Sender: gregames@Mail.MeepZor.Com Message-ID: <3B587F9B.DD0DE3C2@remulak.net> Date: Fri, 20 Jul 2001 14:59:39 -0400 From: Greg Ames X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-3mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: new-httpd@apache.org Subject: Re: apache.org is running the 2.0.21 tarball References: <3B5867F6.EF722B45@remulak.net> <995651394.31667.22.camel@c1619481-a.almda1.sfba.home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Ian Holsman wrote: > > On 20 Jul 2001 13:18:46 -0400, Greg Ames wrote: > > I bounced the httpd server on daedalus over to a build from the new > > apache 2.0.21 tarball as of Friday, 20-Jul-2001 10:12:59 PDT. It looks > > fine, as expected. > what needs to be done to upgrade this to a beta? > are we doing the 'run 3 days on apache.org'' test? Enough people have to vote for it being a beta, and then presto! it is a beta (once we rename it), I believe. As far as the '3 days' test, we've done that already if you count the 2_0_21-dev build, which went up Wednesday PM. cvs has only had small safe changes since. (Ryan must be busy :-) However, I'd like to see us run at least 24 hours on the new tarball before we do anything rash. That puts us into the weekend. Monday would be soon enough for me. But if other folks are really gung ho, I'd be OK with doing it tomorrow (Sat 21 Jul) PM. +1 on beta after 24 hours, btw. Greg