From owner-freebsd-current Fri Jun 12 02:51:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26833 for freebsd-current-outgoing; Fri, 12 Jun 1998 02:51:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26750 for ; Fri, 12 Jun 1998 02:51:27 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id CAA11236; Fri, 12 Jun 1998 02:51:03 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Andrew Specht" cc: freebsd-current@FreeBSD.ORG Subject: Re: current - stable prediction? In-reply-to: Your message of "Fri, 12 Jun 1998 13:30:00 +1000." <029501bd95b2$61995d00$e34a05cb@alpine.iaccess> Date: Fri, 12 Jun 1998 02:51:03 -0700 Message-ID: <11232.897645063@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there an approximate date when 3.0-current will become a stable version? > Or is this to hard to predict at the moment? It's hard to predict. The first release of 3.0 is scheduled for October, but I'm not sure how long after that it will be before we move the -stable tag over to the -current branch. I think it stands to reason that we'll want to have at least one or two releases off the 3.0 line under our belts before we can adequately determine its "stability" in the field, and that's just basic conservatism. I do know of more than one ISP running it right now who swears by it, some of whom report even better results than they had with 2.2.x (there are a few things in 3.0 which are difficult to bring back to 2.2.x but fix substantial problems), but we need more such reports before we can really be sure it's stable enough for -stable. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message