From owner-freebsd-stable Tue Sep 16 12:18:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA14238 for stable-outgoing; Tue, 16 Sep 1997 12:18:24 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA14227 for ; Tue, 16 Sep 1997 12:18:18 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id MAA01555; Tue, 16 Sep 1997 12:18:16 -0700 (PDT) To: "Rodney W. Grimes" cc: freebsd-stable@FreeBSD.ORG Subject: Re: 14 day countdown to BETA In-reply-to: Your message of "Tue, 16 Sep 1997 10:48:29 PDT." <199709161748.KAA06915@GndRsh.aac.dev.com> Date: Tue, 16 Sep 1997 12:18:15 -0700 Message-ID: <1551.874437495@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Great howl of protest: > `` Declare the freeze Sept 20, already 5 days past when it was suppose > to happen, put the tree into ``must be acked by RELENG before commiting > to branch mode until Sept 30, then lock it down to ONLY RELENG can > commit after Sept 30.'' Do you really think that 10 days of "sort of restricted" committing is going to make any substantive difference? I'm kinda skeptical. Essentially, the only difference I can see between your scenario and mine is that I get out the acknowledge-my-ack-or-die stick in 4 days time and start lock-stepping with everyone over each change until the 30th, after which we're talking the same thing. The only problems I see are that a) 4 days is really not enough time for everyone to finish their merging and b) I don't see much substantive difference between "you must acknowledge my ack" and "if I see you put in something dodgy, I'll make you fix it or take it back out." > 15 days is too short a BETA period, given the tree won't be buildable > for more than 50% of the time up until the real code freeze. (3 of my Hmmmm. On the other hand, I'd hate to be distributing 2.2.2 at COMDEX but that's essentially what we're going to be doing unless we get this release out on schedule (and we'll already be a month behind our quarterly release target just releasing in late October as it is). And no, I'm not simply gating our release technology off of the major trade show schedule, I'm simply saying that hawking 6-month old wares at the industry's largest U.S. trade show is not going to be a recipe for success and we should gauge very carefully the effects of additional delay into November. November is also the christmas rush season and it's more than likely that if we decide to do the CDs in November, customers won't see them until January because trying to get our CDs back in December will only elicit howls of laughter from the replication house ("You want it *when*?!"). This not to say that if 2.2.5 were looking majorly broken in October that I'd release it anyway - certainly not. I'm simply saying that pushing it out past the end of October is going to have unpleasant side-effects of its own and we should really try not to do that. Jordan