From owner-freebsd-stable Wed Mar 18 05:11:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29917 for freebsd-stable-outgoing; Wed, 18 Mar 1998 05:11:23 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netcom1.netcom.com (mvh@netcom15.netcom.com [192.100.81.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29906 for ; Wed, 18 Mar 1998 05:11:19 -0800 (PST) (envelope-from mvh@netcom.com) Received: (from mvh@localhost) by netcom1.netcom.com (8.8.8/8.8.8) id FAA02549; Wed, 18 Mar 1998 05:11:14 -0800 (PST) (envelope-from mvh) Date: Wed, 18 Mar 1998 05:11:14 -0800 (PST) Message-Id: <199803181311.FAA02549@netcom1.netcom.com> From: "Michael V. Harding" To: stable@FreeBSD.ORG Subject: 'Code Freeze' Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I'll have to agree with the below - my experience has been that the CDs are the LEAST stable releases. Also, look at this slice code change - it was introduced either after the code freeze, or right before it. The CDs should have a longer test period, maybe a month of real code freeze. I realize that this makes things harder for developers, but the stability of the CD release is very important - this is how most people get introduced to FreeBSD. Absolutely the worst thing any developer can do is to rush code into a release at the last minute. The current practice of announcing release code freezes encourages precisely that bad behavior. The result to a long time CD subscriber like myself is that I have _never_ received a FreeBSD CD that is useful to me by itself. There always seems to be some ugly bug discovered within a month of the CD going to press that requires me to use the CD only as a bootstrap method to get to current STABLE -- which is always reasonably stable, unless Jordan has announced a code freeze recently. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message