From owner-freebsd-current Thu Mar 14 18:43:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 3927B37B647; Thu, 14 Mar 2002 18:37:49 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.6) with SMTP id g2F2aUF06632; Thu, 14 Mar 2002 21:36:31 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Thu, 14 Mar 2002 21:36:30 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Dag-Erling Smorgrav Cc: bmah@FreeBSD.ORG, Peter Wemm , Murray Stokely , current@FreeBSD.ORG, re@FreeBSD.ORG Subject: Re: CVS Issues with branch.. Was: Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" ) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 15 Mar 2002, Dag-Erling Smorgrav wrote: > "Bruce A. Mah" writes: > > Differences of opinion on naming aside...the branch isn't supposed to > > last long at all. The point is to provide a slightly polished snapshot > > to the wider developer community. We can't do the QA/releng work on > > HEAD without calling for a code freeze (which we early on decided that > > we would *not* do). > > Then you don't need a branch, you just need a simple tag, and you can > slide it forward if something needs fixing, and remove it after rolling > and shipping the snapshot. No, in this case that doesn't help. What we want is to grab a stable moment, then to allow development to continue. However, we may then want to tweak that stable moment without impinging on development, which requires a branch. The QA/releng work requires us to modify the stuff being released following the branchpoint. It's worth noting, BTW, that originally the release engineering team planned to use Perforce for this to avoid the branch issue entirely, minimize impact on the main tree, etc, but decided not to due to the high volume of complaints on the topic. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message