From owner-freebsd-stable@FreeBSD.ORG Tue Apr 1 11:54:49 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 0A13337B445 for ; Tue, 1 Apr 2003 11:54:49 -0800 (PST) Received: from trillian.santala.org (ip212-226-173-33.adsl.kpnqwest.fi [212.226.173.33]) by mx1.FreeBSD.org (Postfix) with SMTP id 6328043F93 for ; Tue, 1 Apr 2003 11:54:47 -0800 (PST) (envelope-from jake@iki.fi) Received: (qmail 4970 invoked by uid 11053); 1 Apr 2003 19:54:44 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Apr 2003 19:54:44 -0000 Date: Tue, 1 Apr 2003 22:54:44 +0300 (EEST) From: Jarkko Santala X-X-Sender: jake@trillian.santala.org To: Kirk Strauser In-Reply-To: <87znnaw7vq.fsf@pooh.honeypot.net> Message-ID: <20030401224035.R474@trillian.santala.org> References: <20030401141454.N43325-100000@atlantis.atlantis.dp.ua> <87znnaw7vq.fsf@pooh.honeypot.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-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: Tue, 01 Apr 2003 19:54:49 -0000 On Tue, 1 Apr 2003, Kirk Strauser wrote: > At 2003-04-01T11:30:15Z, Dmitry Pryanishnikov writes: > > > I see 4.8-RELEASE is already available on ftp://ftp.freebsd.org... > > No, it's not. Until 4.8 is officially announced, what you see is only some > files that *may* turn out to be 4.8-RELEASE, but could just as easily be > wiped and replaced with something different. IMHO _nothing_ should be called X.Y-RELEASE unless it is truly X.Y-RELEASE. This goes for any files on ftp and any cvs repositories. Once you tag something as X.Y-RELEASE or once you make any files public with that name on it, it becomes that release. If something comes up after the tag has been made in cvs (which, of course, should be done before any distributions are created and any files are available anywhere), it has to go into p1 or X.Y.Z. This is exactly why Release Candidates exist. Ideally the release should be exactly the same as the last RC. And since we're talking about non-commercial software here, there should be no pressure in releasing anything until it really is ready. These are, naturally, just my own opinions based on my limited experiences in doing release engineering elsewhere and should not be considered as absolute truth. :) All said applies only to open source projects where cvs repositories and files are publicly available, in commercial environments moving a release tag may be acceptable for commercial reasons, which of course do not exist in non-commercial projects. -jake ps. this email was written on a box that has been running 4.8-RELEASE for over a day. I'll be a very sad puppy if someone moves the tag now. :'( -- Jarkko Santala http://www.iki.fi/~jake/ System Administrator 2001:670:83:f08::/64