From owner-freebsd-current Tue Oct 12 10: 6:39 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 C23C915BA9 for ; Tue, 12 Oct 1999 10:06:34 -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 TAA25328; Tue, 12 Oct 1999 19:03:37 +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 09:54:02 PDT." Date: Tue, 12 Oct 1999 19:03:37 +0200 Message-ID: <25326.939747817@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: >> "This time of the year" == "This time in the release cycle" >> >> If we want to have a somewhat clean line before 4.0 now is the time >> to push it through, not after the code freeze. > >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. -- 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