From owner-freebsd-current  Sun May  2 12:41:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from blackhelicopters.org (unknown [209.69.178.18])
	by hub.freebsd.org (Postfix) with ESMTP id DC8B9151AA
	for <freebsd-current@freebsd.org>; Sun,  2 May 1999 12:41:52 -0700 (PDT)
	(envelope-from dispatch@blackhelicopters.org)
Received: (from dispatch@localhost)
	by blackhelicopters.org (8.8.8/8.8.8) id PAA22423
	for freebsd-current@freebsd.org; Sun, 2 May 1999 15:41:51 -0400 (EDT)
	(envelope-from dispatch)
From: Dispatcher <dispatch@blackhelicopters.org>
Message-Id: <199905021941.PAA22423@blackhelicopters.org>
Subject: Re: -stable vs -current (was Re: solid NFS patch #6... )
To: freebsd-current@freebsd.org
Date: Sun, 2 May 1999 15:41:51 -0400 (EDT)
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

#Tim Vanderhoek wrote:
#On Fri, Apr 30, 1999 at 04:52:58PM -0700, Matthew Dillon wrote:
#> 
#>     I expect the 3.2 release to be a really good release.
#
#I seem to recall that 2.2.x wasn't even called "-stable" until 2.2.2.
#That .2 release is exactly where 3.x is right now...

And it wasn't until 2.2.5 that I saw an official note saying "2.1.7
users should upgrade now."  I won't upgrade my mission-critical
systems until I see a similar notice from Jordan or someone in his
place.

For mission-critical systems, I'm still installing 2.2.8-stable.

==ml


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message