From owner-freebsd-qa Thu Dec 23 18:59: 0 1999 Delivered-To: freebsd-qa@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id EE80815122; Thu, 23 Dec 1999 18:58:57 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19991224025649.ODYH7552.mail.rdc3.on.home.com@tristan.net>; Thu, 23 Dec 1999 18:56:49 -0800 Content-Length: 1400 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <11234.945929164@zippy.cdrom.com> Date: Thu, 23 Dec 1999 21:56:03 -0500 (EST) From: Colin To: "Jordan K. Hubbard" Subject: Re: After 3.4 finally goes out the door Cc: "jkh@freebsd.org" , freebsd-qa@FreeBSD.ORG, Jason Young Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm in for a longer adventure, but I'm not sure 30 days is workable. Ideally we'd have a freeze at the start of the test phase, and I can't see a 30 day freeze working in this environment ;) I think we saw what happened when we tried testing against a moving target. I honestly don't know what the answer is, maybe tighter control over changes and additions after we enter the test phase without a real freeze? Maybe there is a way to do a freeze? The other point we should be aware of is that starting in Jan, most of us (I assume most of the people on this list are in the IT industry somewhere ;)) can expect to get really busy as the Y2K panic ends and businesses get back to upgrading and buying new stuff. Time for volunteering might get a bit tight ;) Assuming my day job doesn't kill me, I'lll even attempt some code for testing specific functionality. I'm open to ideas for this, I've already started mapping out some code to test threads and the file system, and I should have something to play with before end month. I really had no (and am still a bit vague on) ideas for what needs testing. cheers, Colin Jordan wrote... > All I can say is that mistakes were made and learned from, in some > cases for the 2nd or 3rd time (*urk*), and 3.5 will come out with a > very very different and somewhat elongated release schedule as a > result. Shall we say 30 days? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message