From owner-freebsd-questions Wed Jan 5 15:16:21 2000 Delivered-To: freebsd-questions@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id A06B4154F2 for ; Wed, 5 Jan 2000 15:16:11 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.092 #1) id 125yHb-00019V-00; Wed, 05 Jan 2000 21:47:55 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.092 #1) id 125yHb-0003pZ-00; Wed, 05 Jan 2000 21:47:55 +0000 Date: Wed, 5 Jan 2000 21:47:55 +0000 From: Ben Smithurst To: Chris.Smith@raytheon.co.uk Cc: freebsd-questions@freebsd.org Subject: Re: Any Ideas When We're Going to See 4.0-RELEASE? Message-ID: <20000105214755.C14126@strontium.scientia.demon.co.uk> References: <0025685D.0052E516.00@rslhub.raytheon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <0025685D.0052E516.00@rslhub.raytheon.co.uk> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris.Smith@raytheon.co.uk wrote: > Pending a major upgrade, is there any chance of 4.0-RELEASE being knocked > out soon, or shall I just update to 3.4? jkh just posted this to -current: | Subject: 4.0 code freeze scheduled for Jan 15th | To: committers@freebsd.org | Cc: current@freebsd.org | Message-ID: <28153.947101446@zippy.cdrom.com> | | And given that we've already slipped from December 15th, I think you | can treat this as a pretty hard deadline, to be further slipped only | grudgingly and in response to clear and dire need. | | 10 days, folks! Make 'em count.. :) | | The code freeze will last for 15 days, during which time the 4.0 simple arithmetic tells me 4.0 is scheduled for Jan 30th. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message