From owner-freebsd-qa Sat Dec 25 12: 0:31 1999 Delivered-To: freebsd-qa@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1DC0A14EDB; Sat, 25 Dec 1999 12:00:29 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA57643; Sat, 25 Dec 1999 12:00:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Colin Cc: "jkh@freebsd.org" , freebsd-qa@FreeBSD.ORG, Jason Young Subject: Re: After 3.4 finally goes out the door In-reply-to: Your message of "Thu, 23 Dec 1999 21:56:03 EST." Date: Sat, 25 Dec 1999 12:00:38 -0800 Message-ID: <57639.946152038@zippy.cdrom.com> From: "Jordan K. Hubbard" 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. Well, 30 days is workable if it's a real freeze, and that was something I also forgot to mention in my previous missive - we'd be going to a *real* freeze structure, not the half tongue-in-cheek "code slushes" I've been calling lately. A code slush might be appropriate for -current pending a dot-zero release, that much I can see, but anything less than a hard freeze for -stable pending a release just isn't going to fly in the future. In my eagerness to get rid of a really annoying and long-standing problem, I also broke too many of my own rules for last-minute tweaking with sysinstall in 3.4 and I don't intend to make that mistake again. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message