From owner-freebsd-stable Thu Mar 19 22:15:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03108 for freebsd-stable-outgoing; Thu, 19 Mar 1998 22:15:40 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netcom1.netcom.com (mvh@netcom6.netcom.com [192.100.81.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03094 for ; Thu, 19 Mar 1998 22:15:32 -0800 (PST) (envelope-from mvh@netcom.com) Received: (from mvh@localhost) by netcom1.netcom.com (8.8.8/8.8.8) id WAA20223; Thu, 19 Mar 1998 22:15:26 -0800 (PST) (envelope-from mvh) Date: Thu, 19 Mar 1998 22:15:26 -0800 (PST) Message-Id: <199803200615.WAA20223@netcom1.netcom.com> From: "Michael V. Harding" To: john@www.cas.unt.edu CC: freebsd-stable@FreeBSD.ORG In-reply-to: <199803191903.NAA25509@www.cas.unt.edu> (message from john on Thu, 19 Mar 1998 13:03:59 -0600 (CST)) Subject: Re: 'Code Freeze' References: <199803191903.NAA25509@www.cas.unt.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Actually - I would differ on this. 'stable' users are, in a sense, the worst people to test the install procedure. The best way to test would be to use actual CDs and do fresh installs. By definition, stable users generally aren't doing a clean install, and know what they're doing. One more pet peeve - can the binaries for the ports be left on cdrom.com at least until the next release? I've lent CDs to people who aren't up to going -stable yet, and a remarkable number of the ports can't be built because the binaries can't be fetched. OK, no more cranking - I am just nit picking because there are really only nits to pick! Keep up the good work all - I'll be building world tonight... Mike Harding From: john Date: Thu, 19 Mar 1998 13:03:59 -0600 (CST) Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-UIDL: 40d0a0c9136f6248a249b13788873a2b > > Anyways, with CD burners as cheap as they are - how about a test run??? > You wouldn't event need to burn a CD, you could just have FreeBSD x.x.x release candidate #x where you may have a few release candidates before an actual release. Now I guess -stable is supposed to be the release candidates but if changes get rammed thru and aren't adequately tested then the release may not be stable. I know I don't update my -stable very often at all. Once I've got a stable -stable I tend to ride it out till after the next release then wait for the next -stable to seeem up to snuff. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message