From owner-freebsd-current Fri Oct 16 19:27:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13622 for freebsd-current-outgoing; Fri, 16 Oct 1998 19:27:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13610 for ; Fri, 16 Oct 1998 19:26:57 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id VAA12979; Fri, 16 Oct 1998 21:26:17 -0500 (CDT) Received: from harkol-60.isdn.mke.execpc.com(169.207.64.188) by peak.mountin.net via smap (V1.3) id sma012976; Fri Oct 16 21:25:46 1998 Message-Id: <3.0.3.32.19981016212053.00f51c60@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 16 Oct 1998 21:20:53 -0500 To: Mike Smith From: "Jeffrey J. Mountin" Subject: Re: R-Day, 15th October, 1998 (BST or similar ;-) Cc: Mike Smith , "Jordan K. Hubbard" , Karl Pielorz , current@FreeBSD.ORG In-Reply-To: <199810160547.WAA00764@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:47 PM 10/15/98 -0700, Mike Smith wrote: >It looks like there will be a snapshot of FreeBSD/Alpha at about the >3.0-RELEASE level, out at about the same time. I don't think it will >be described as RELEASE quality (we're not a Linux vendor after all). So 3.0-RELEASE is a release, but not of the normal variety. >The new loader will be installed. The new boot blocks will be >available, but will not be installed. The new loader will not be >*used* by default. Gotcha. >> Further will 'make world'/'make buildworld' automagically install the new >> load on 3.0 if the sysinstall does not? > >Yes. Following what sysinstall does in the first place. >The principal goals for the next few months will be to complete the >current development push and stabilise the existing feature set. We'll >branch before 3.0.5 or whatever it's called in February or so, at which >point aggressive development will move to the 3.1 branch and the >-stable tag will transition to the 3.0.x branch. Ah, so the 3.x -stable branch will not appear for while and RELENG_3(?) won't appear for a while. Been expecting to cvsup from -current anyways should there be any issue. >As Jordan has already expounded, the 3.0-RELEASE is meant to put the >mostly-complete current feature set out to a wider audience; to get it >used in real-world conditions and on the radar screens of commercial >vendors, etc. It holds much of the shape of things to come in many >ways, even though it is in and of itself not a complete thing. Fully understood and plan to run with it on a fairly loaded dual-PPro web server. They way things look now, any problems should be related to the site's cgi, which is undergoing a rewrite by myself to fix some problems. "FreeBSD, no warranty, no official tech support, but assures satisfaction." 8-) Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message