From owner-freebsd-isp Sun Oct 18 08:50:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02118 for freebsd-isp-outgoing; Sun, 18 Oct 1998 08:50:13 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02112 for ; Sun, 18 Oct 1998 08:50:11 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbws.vastnet.net (port25.netsvr1.cst.vastnet.net [207.252.73.25]) by etinc.com (8.8.8/8.6.9) with SMTP id LAA13775; Sun, 18 Oct 1998 11:47:49 GMT Message-Id: <3.0.32.19981018114951.00723bc8@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 18 Oct 1998 11:49:54 -0400 To: Bill Vermillion , freebsd-isp@FreeBSD.ORG From: Dennis Subject: Re: Don't bet on 3.0 release Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 10:37 AM 10/18/98 -0400, Bill Vermillion wrote: >Greg Lehey recently said: >> On Sunday, 18 October 1998 at 0:18:51 +0100, Karl Pielorz wrote: > >> > Paul Stewart wrote: > >> >> We just upgraded our main commerical web server to 3.0-RELEASE >> >> and everything works like a dream except I can't compile >> >> apache-ssl for our secure server... as it's compiling, I get >> >> the following from the SSLeahy port... > >> > Not wanting to start fireworks, but if it's your _main_ >> > commercial / production box you probably shouln't have done >> > that... If you look through the -current mailing list you would >> > have seen why... A lot of the ports, and other software have >> > problems with ELF at the moment... > >> To be fair, 3.0 has now been released, and you can't expect that >> everybody who's now thinking of installing to have been reading >> -current all this time. > >Well there was plenty of notice/warning about 3.0 being the first >cut and was to be for experimentors and early adopters. I got a >notice on my subscription about 2 months ago - and they suggested >that you wait until at least 3.1 for a production environment. > >Installing a new release on a production system within days of its' >release always has the chance of being dicey. No matter how much >you beta test something still seems to come out that was missed. -RELEASE implies that its ready for the general public. If its still in BETA, which your comments indicate it is, then it should not be released. What's the point of doing a release if its not ready? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message