From owner-freebsd-qa Wed Oct 25 6:20:39 2000 Delivered-To: freebsd-qa@freebsd.org Received: from spoon.beta.com (064-184-210-067.inaddr.vitts.com [64.184.210.67]) by hub.freebsd.org (Postfix) with ESMTP id EC9CE37B4C5 for ; Wed, 25 Oct 2000 06:20:37 -0700 (PDT) Received: from spoon.beta.com (localhost [127.0.0.1]) by spoon.beta.com (8.11.0/8.11.0) with ESMTP id e9PDKau24427 for ; Wed, 25 Oct 2000 09:20:37 -0400 (EDT) (envelope-from mcgovern@spoon.beta.com) Message-Id: <200010251320.e9PDKau24427@spoon.beta.com> To: qa@freebsd.org Subject: 4.2 Freeze 11/7... Date: Wed, 25 Oct 2000 09:20:36 -0400 From: Brian McGovern Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't seen much traffic on this list since I've seen word of the code freeze, so I guess I'll do my standard "project kickoff" to try to get some time on 4.2 before it ships. Now that I have an operating work space again, I can be a little more active... Based on the fact my personal preference is to take build 3-4 days apart to give developers a chance to fix anything we find before we have to do another download and test cycle, I suggest (and I will look at) the following -CURRENT snapshots as test candidates: 10/27 10/31 11/3 11/6 Code freezes on 11/7. We should therefore also grab the 11/8, and treat it as a release candidate. Can I get a roll call from people who will be able to work this plan, so I can tell how many eyes will be on it? -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message