From owner-freebsd-stable@FreeBSD.ORG Wed Apr 2 20:26:10 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B538C37B401 for ; Wed, 2 Apr 2003 20:26:10 -0800 (PST) Received: from smtp-relay.omnis.com (smtp-relay.omnis.com [216.239.128.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4B1543FB1 for ; Wed, 2 Apr 2003 20:26:09 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.homeunix.net (66-91-236-204.san.rr.com [66.91.236.204]) by smtp-relay.omnis.com (Postfix) with ESMTP id D748143881; Wed, 2 Apr 2003 20:26:04 -0800 (PST) From: Wes Peters Organization: Softweyr To: Andy Sparrow , Gunnar Flygt Date: Wed, 2 Apr 2003 20:26:02 -0800 User-Agent: KMail/1.5 References: <20030402082621.7A80A9E@CRWdog.demon.co.uk> In-Reply-To: <20030402082621.7A80A9E@CRWdog.demon.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304022026.02927.wes@softweyr.com> cc: stable@freebsd.org Subject: Re: 4.8-RELEASE vs SA-03:07 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 04:26:11 -0000 On Wednesday 02 April 2003 00:26, Andy Sparrow wrote: > > I don't really understand why the Release Engineering is done the way > it is. When I was releasing commercial software, I'd simply lock and > tag the tree with a unique, temporary, label, check out a clean tree > against that label, unlock the tree and build and package the software. When you were releasing commercial software, you probably weren't working with a team of 200+ developers scattered all over the globe, working in most every timezone, most of whom have never met each other face to face. The "gating effect" enforced by the way FreeBSD does releases helps everyone involved in the process spend a bit of time twice a year on bringing development work back to a stable focal point. This is not a bad thing. Long-term development projects are handled on long-lived branches like the initial 5.x branch; several development projects are already waiting in the wings for 6-current as soon as 5-current becomes 5-stable. This procedure isn't set in stone, we're still learning as we go here, but there is SOME method to our madness. If you want to dive into the process and get your hands dirty, send email to re@ AFTER the release is done. I'm sure you can find some way to help. Just don't pester them at the moment, unless you know of a driver or two that can be hacked out, OK? ;^) -- Where am I, and what am I doing in this handbasket? Wes Peters wes@softweyr.com