From owner-freebsd-chat Thu Jun 4 21:06:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20369 for freebsd-chat-outgoing; Thu, 4 Jun 1998 21:06:14 -0700 (PDT) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from lariat.lariat.org (ppp1000.lariat.org@lariat.lariat.org [129.72.251.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20298 for ; Thu, 4 Jun 1998 21:06:00 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.8) id WAA19723; Thu, 4 Jun 1998 22:05:52 -0600 (MDT) Message-Id: <4.0.1.19980604174542.044f7310@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Thu, 04 Jun 1998 17:55:18 -0600 To: chat@FreeBSD.ORG From: Brett Glass Subject: FreeBSD 2.99999? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got a quandary on my hands. I need to deploy a new UNIX server, and would like to run FreeBSD on it. I could run 2.2.6 (with patches -- unless a 2.2.7 is imminent) on it, or risk going to 3.0-current. 2.2.6 is fabulously stable, but -current has so many appealing features that are not being migrated back to 2.2.x (for instance, CAM, DOS VMs, long user names, 64-bit dates, etc.) that I'd be sacrificing a lot if I installed 2.2.6. And installing a snapshot (as I've done in the past) can be risky and messy. (Sticking with a relatively stable snap and using CVSup each have benefits and liabilities.) How far is 3.0 away from prime time? What is the official criterion for deciding when it's ready to do a release? Now that it has so many things that 2.2.6 doesn't, is it time for a 2.9999 release based on the -current source tree to wring out the remaining bugs? --Brett Glass To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message