From owner-freebsd-stable@FreeBSD.ORG Tue Apr 1 13:20:45 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 687DC37B401 for ; Tue, 1 Apr 2003 13:20:45 -0800 (PST) Received: from conn.mc.mpls.visi.com (conn.mc.mpls.visi.com [208.42.156.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8D3143F3F for ; Tue, 1 Apr 2003 13:20:44 -0800 (PST) (envelope-from veldy@veldy.net) Received: from veldy.net (veldy-host33.dsl.visi.com [209.98.200.33]) by conn.mc.mpls.visi.com (Postfix) with ESMTP id 0DA9C828B; Tue, 1 Apr 2003 15:20:44 -0600 (CST) Received: from VELDYT (localhost [127.0.0.1]) by veldy.net (Postfix) with SMTP id 30A552E8; Tue, 1 Apr 2003 15:20:43 -0600 (CST) Message-ID: <00eb01c2f894$7d5efaa0$0a05010a@VELDYT> From: "Thomas T. Veldhouse" To: , "Kirk Strauser" References: <20030401141454.N43325-100000@atlantis.atlantis.dp.ua><87znnaw7vq.fsf@pooh.honeypot.net><20030401224035.R474@trillian.santala.org> <87u1diufey.fsf@pooh.honeypot.net> Date: Tue, 1 Apr 2003 15:20:15 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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 21:20:45 -0000 Such software could be written ... :) Tom Veldhouse ----- Original Message ----- From: "Kirk Strauser" To: Sent: Tuesday, April 01, 2003 2:32 PM Subject: Re: 4.8-RELEASE vs SA-03:07 At 2003-04-01T19:54:44Z, Jarkko Santala writes: > 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. I understand the point you want to make, but there are some subtle issues. Foremost is that there are many mirrors of the main FTP server. The release team will upload the final product and let the mirrors fetch a copy before announcing it officially so that it's available on all of the mirrors the moment the message is sent. There's no great way around that unless you can convince all of your mirrors to download `giant-unnamed-tarball.tar.gz' and then simultaneously rename it to `freebsd-4.8-release.tar.gz' when the release team hits the "Send" button. -- Kirk Strauser In Googlis non est, ergo non est.