Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 21844 invoked by uid 6000); 26 Mar 1999 15:49:39 -0000 Received: (qmail 21699 invoked from network); 26 Mar 1999 15:49:33 -0000 Received: from i.meepzor.com (HELO Mail.MeepZor.Com) (root@204.146.167.214) by taz.hyperreal.org with SMTP; 26 Mar 1999 15:49:33 -0000 Received: from Golux.Com (ss03.nc.us.ibm.com [32.97.136.233]) by Mail.MeepZor.Com (8.8.5/8.8.5) with ESMTP id KAA13434; Fri, 26 Mar 1999 10:52:16 -0500 Message-ID: <36FBAC7E.37FFFCE1@Golux.Com> Date: Fri, 26 Mar 1999 10:49:18 -0500 From: Rodent of Unusual Size Organization: The Apache Group X-Mailer: Mozilla 4.06 [en] (WinNT; U) MIME-Version: 1.0 To: new-httpd@apache.org Subject: Re: cvs commit: apache-1.3 STATUS References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Roy wrote: > > Ken, the website is supposed to be updated a FULL DAY BEFORE the > announcement. Yup. And the copy in CVS is frequently committed several days in advance, and only activated with a 'cvs update' when the release is actually ready. Since it didn't look like the release had gone out, it appeared that the update had been done prematurely. Lars Eilebrecht wrote: > > According to Rodent of Unusual Size: > > > The STATUS file indicates it hasn't been announced yet. It says > > 1.3.6-dev is the current release. I haven't seen anything sent > > I just updated STATUS... Right after I released 1.3.6 (yes > 1.3.6 *is* out) one of my hard disks (the one with /home) died with > a hardware failure and I wasn't able to update STATUS earlier. I'm > still trying to recover from the crash (my DAT drive went *kaboom* > last week and I cannot access my backup tapes). :-/ Wow, you have *backups*? :-) > > more than a handful of binaries ready, and they haven't > > been moved into /dist/binaries/*/ yet. > > We've currently 17 binary dists and I moved all available > dists from the dev site to /dist/binaries on the 24th. > I wasn't able to copy your freebsd dist, because permissons > where set to 600. I posted a note about this to new-httpd > three days ago. I fixed it within an hour of receiving the message; I mv'd them yesterday w/o changing the permissions, which show as 775 -- so I don't know what went wrong. It wasn't clear from your message that we were supposed to move them after fixing the perms.. sorry. > Aren't you reading apache-cvs?? Yup, but see my note above about commits versus updates. > No offense, but nobody should ever change anything regarding > the release version before talking with the release manager! Absolutely. Mea maxima culpa. :-( -- #ken P-)} Ken Coar Apache Group member "Apache Server for Dummies"