From owner-freebsd-current Thu Jun 27 14:40:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA28316 for current-outgoing; Thu, 27 Jun 1996 14:40:49 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA28307 for ; Thu, 27 Jun 1996 14:40:41 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id OAA01464; Thu, 27 Jun 1996 14:39:20 -0700 (PDT) To: Nate Williams cc: current@FreeBSD.org Subject: Re: Shakeout time for -stable? In-reply-to: Your message of "Thu, 27 Jun 1996 10:57:23 MDT." <199606271657.KAA10357@rocky.mt.sri.com> Date: Thu, 27 Jun 1996 14:39:19 -0700 Message-ID: <1460.835911559@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Is there a plan to have a waiting period for things to 'shake out' > before the CD is cut with 2.1.5? With all of the significant 'new' > stuff and changes that have gone in the last 72 hours (VM/random in > particulr), I'd like to have time to beat on my -stable boxes to make > sure nothing got broken. I think the code-freeze is still well-advised, > but I think at least a couple weeks of shakeout time to get things beat > up well and good would be advisable. I'd *hate* to have this release Well, I'm not sure if we have a couple of weeks (we're already 7 days late on just the "BETA") but I've released a 2.1-960627-SNAP today which I hope to get some testing on. It's uploading now and when the directory permissions are not 700, that means its ready for testing. I do think the essence of Nate's argument is correct, and I can only suggest that we do some very *accellerated* testing so that we can both get this baby out on schedule (David and I are VERY eager to get back to 2.2 hacking) and make it a good release. Jordan