From owner-freebsd-current Sun May 2 15:54:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 6811114E7A for ; Sun, 2 May 1999 15:54:25 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA25594; Sun, 2 May 1999 15:54:13 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Dispatcher Cc: freebsd-current@FreeBSD.ORG Subject: Re: -stable vs -current (was Re: solid NFS patch #6... ) In-reply-to: Your message of "Sun, 02 May 1999 15:41:51 EDT." <199905021941.PAA22423@blackhelicopters.org> Date: Sun, 02 May 1999 15:54:13 -0700 Message-ID: <25590.925685653@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. And I can only echo these sentiments. I've never made a secret of the fact that ".5" is always the best time to jump on board any branch in this project and it's been that way since practically the beginning. There's even a later snapshot release of the 2.2 branch on the FreeBSD Toolkit for people who continue to subscribe to this philosophy. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message