From owner-freebsd-current Mon Aug 4 07:53:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA04070 for current-outgoing; Mon, 4 Aug 1997 07:53:03 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA04065 for ; Mon, 4 Aug 1997 07:53:01 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id HAA01027; Mon, 4 Aug 1997 07:52:09 -0700 (PDT) To: Mark Huizer cc: Wolfgang Helbig , current@FreeBSD.ORG Subject: Re: Current is currently really a mess (was: Re: Tk/Tcl broken(?)) In-reply-to: Your message of "Mon, 04 Aug 1997 16:42:38 +0200." <19970804164238.16405@xaa.stack.nl> Date: Mon, 04 Aug 1997 07:52:09 -0700 Message-ID: <1023.870706329@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Well... I would seriously dislike the idea of ports not working on current, > since I run that at home. But I like ports for stable too, since I run it > on cvsup.nl.freebsd.org. But that's only two releases. What about 2.1.*? Well, I see FreeBSD has having 3 branches at any given time: current: Bleeding edge. stable: The release branch, AKA "stable" after a short transition. legacy: The previous release branch in phase-out mode. We've confused things more than a little bit in the past by calling both the legacy branch and the release branch "stable", but I think we've learned from that experience and can start using less confusing nomenclature in the future. In any case, I don't see maintaining ports for anything but -stable as useful or necessary, the -current people basically using the -stable ports tree for as long as it works (and the current fracas with TCL aside, it largely *does* work even now if you go by straight percentages). Once we started getting reasonably close to rotating stable to legacy and current to stable, that's when we'd transition the ports/packages collection to the new stable branch and fix up whatever broke before finally doing a combined release. Jordan