From owner-freebsd-current Thu Oct 8 20:48:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07982 for freebsd-current-outgoing; Thu, 8 Oct 1998 20:48:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA07858 for ; Thu, 8 Oct 1998 20:48:08 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zRTX0-0005F7-00; Thu, 8 Oct 1998 21:47:54 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id VAA09346 for ; Thu, 8 Oct 1998 21:47:31 -0600 (MDT) Message-Id: <199810090347.VAA09346@harmony.village.org> Subject: Re: Code freeze (was: Is tickadj still required in -CURRENT ?) To: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 09 Oct 1998 10:33:42 +0930." <19981009103342.E3369@freebie.lemis.com> References: <19981009103342.E3369@freebie.lemis.com> <199810081920.MAA23658@austin.polstra.com> Date: Thu, 08 Oct 1998 21:47:31 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last time I checked, we were not in code freeze. We have been in a feature freeze since Sept 15, but new features have been added since then, by special arrangement with the release engineer. Code freeze doesn't happen until on or about Oct 15 when Jordan starts the release process, assuming that we're ready. : I suppose the next question is "When are we going to start Beta?" When 3.0.0 ships, just like everyone else in the biz :-). Back when Jordan announced this date, it was made clear that we can do this now, so we can get into line for pressing CDs for the xmas rush, or we wait until approximately February to make the release. The window to do a release this year and have CDs before January is closing. I don't think there is anything so majorly broken with with FreeBSD to slip the release out 5 months. From my vantage point, 3.0.0 appears like it is going to be fairly stable, but rough around many edges. In the absense of the CD pressing windows, I'd likely argue slipping things out about a month given the level of activity that I'm seeing in the commit messages. It isn't the best possible way of doing a release, but it I find it to be good enough, especially for an organization like FreeBSD. In many ways 3.0 represents such a large improvement in so many areas that it is likely going to be a win to get it out sooner rather than later. The only reason to hold up FreeBSD 3.0.0 that I can think of is if there is some huge, ugly data corruption bug (or similar) that needs to be killed. All of this is just IMHO. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message