From owner-freebsd-arch Sat Oct 12 14:57:45 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FC3037B401 for ; Sat, 12 Oct 2002 14:57:44 -0700 (PDT) Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A1EB43E7B for ; Sat, 12 Oct 2002 14:57:43 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g9CLvfh1282038 for ; Sat, 12 Oct 2002 17:57:41 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <3DA7C3DF.1CFD6978@softweyr.com> References: <200210112056.g9BKuZEx041686@apollo.backplane.com> <3DA7C3DF.1CFD6978@softweyr.com> Date: Sat, 12 Oct 2002 17:57:41 -0400 To: arch@FreeBSD.ORG From: Garance A Drosihn Subject: Re: 6.0 branching (no longer: HEADS UP: 5.0 Feature Freeze October 16, 2002) Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 11:40 PM -0700 10/11/02, Wes Peters wrote: >I think we need to discuss when we will branch 6.x. I think we need >to wait until we have a 5.x release that is stable enough to consider >for production workstation usage levels, and hope we may reach that >point by the 5.2 release. It is good to explicitly say something about this topic now, so people don't think a 6.0-current branch is going to happen right away. That said, the decision of exactly *when* to do the branch can only be guessed at right now. Right now we can say that 5.0-release will not be quite production-quality enough for a new 6.0 branch at that time. If we find that 5.1-release is production quality, then we should do the branch then. If it is not production-quality, then we should wait until after 5.2-release. If 5.2 is not production quality, then we will have to wait some more, no matter what hopes we have for 5.2 as we sit here talking about it before 5.0-release is even out the door. We should be clear that the criteria is "5.x is production quality", and not "when .x reaches .2". At some point (which might be 5.1) it will probably be helpful to have an explicit list of what issues need to be fixed before we can make the new -current branch. Let me also invoke the popular image of herding cats, and point out that "the project" can only hold off from making an official branch for so long before individual developers are going to feel that they (personally) have to start working on the Next Great Thing, and they will start doing private branches using their own source repositories. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message