From owner-freebsd-current Tue Oct 12 10:18:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2382814C41 for ; Tue, 12 Oct 1999 10:18:15 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA25390; Tue, 12 Oct 1999 19:16:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: "Daniel C. Sobral" , Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: scsi tape driver wants an update In-reply-to: Your message of "Tue, 12 Oct 1999 10:12:54 PDT." Date: Tue, 12 Oct 1999 19:16:26 +0200 Message-ID: <25388.939748586@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: > >> >And could you mention when the code freeze might be so that some of us >> >could plan our work? Perhaps I've missed something, but I hadn't heard >> >when the freeze would be. I have a *lot* of things to consider changing >> >before it. >> >> I have no idea when the code freeze happens, neither has anybody else. >> >> Looking at my complete collection of FreeBSD CDs on the shelf here >> I would put my money (but not too much) on january 2000. > >Well, you scared me with the "not after the code freeze" statement. I >would like the work I do for FreeBSD 4.0 not to be as incomplete as it was >for FreeBSD 3.0, so making plans as to when new feature freeze is would be >a "good thing (tm)". I'd say try to have the boat rocking done by dec 1st, but that is merely a guess. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message