From owner-freebsd-stable Mon Nov 18 14:36:10 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E075437B401; Mon, 18 Nov 2002 14:36:06 -0800 (PST) Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49F6F43E3B; Mon, 18 Nov 2002 14:36:05 -0800 (PST) (envelope-from manek@ecst.csuchico.edu) Received: from user-38ldt0e.dialup.mindspring.com ([209.86.244.14] helo=rover) by hawk.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 18DuUr-0000u0-00; Mon, 18 Nov 2002 14:36:01 -0800 From: "Sameer R. Manek" To: Cc: Subject: restoring definition of -stable Date: Mon, 18 Nov 2002 14:36:00 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <20021117224945.A806@grosbein.pp.ru> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Eugene Grosbein > > I wonder why no one says that -STABLE really WAS stable and WAS intended > for end users less than 2 years ago. Moreover, Hanbook said you > need -STABLE if you are using FreeBSD in production environment > and you need stability, Handbook said it even 15 months ago. > And it has been assetring so for long time, that's where the name > of this branch came from. Anyone can see that in CVS. > cc'd to release engineering team I think part of the problem is that freebsd has lost someone who previously used to make sure that patches MFC were actually stable. JKH used to play an active role in that. I remember once, someone had MFC some code that introduced a stability bug, Jordan told the list that whoever MFCd' the code had till the end of the day to issue a fix, or roll back the patch. We all agree that -current is never a good idea for production systems. The definition of what is -stable has been relaxed in the past 2 years. If you look at the handbook from 2 years ago, you will see this is what they define it as. I request that the release engineering team please attempt to restore this definition of -stable, which imho is a far more responsible definition. Since the only patches issued for a -release are security patches, not bug fixes, users of stable systems need a means of applying patches, waiting for the next -release is not the option. http://www.freebsd.org/cgi/cvsweb.cgi/doc/en_US.ISO8859-1/books/handbook/cut ting-edge/chapter.sgml?rev=1.35&content-type=text/x-cvsweb-markup Who needs FreeBSD-stable? If you are a commercial user or someone who puts maximum stability of their FreeBSD system before all other concerns, you should consider tracking stable. This is especially true if you have installed the most recent release -RELEASE at the time of this writing) since the stable branch is effectively a bug-fix stream relative to the previous release. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message