From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 05:23:20 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 82A2337B401 for ; Sun, 8 Jun 2003 05:23:20 -0700 (PDT) Received: from sentry.24cl.com (174.113.sn.ct.dsl.thebiz.net [216.238.113.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id B69BE43F93 for ; Sun, 8 Jun 2003 05:23:19 -0700 (PDT) (envelope-from zlists@mgm51.com) Received: from winbloat (winbloat.24cl.home [10.0.1.10]) by sentry.24cl.com (Postfix) with ESMTP id 8806029437 for ; Sun, 8 Jun 2003 08:23:18 -0400 (EDT) Message-ID: <200306080823180609.002CD0F6@sentry.24cl.com> In-Reply-To: <002901c32d48$7d39c8a0$dd8616c3@rmto90894701> References: <20030607152936.D24263-100000@cobble.capnet.state.tx.us> <00f801c32d39$1f230380$dd8616c3@rmto90894701> <20030607215631.GB97015@laptop.lambertfam.org> <002901c32d48$7d39c8a0$dd8616c3@rmto90894701> X-Mailer: Calypso Version 3.20.01.01 (4) Date: Sun, 08 Jun 2003 08:23:18 -0400 From: "MikeM" To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="ISO-8859-1" Subject: Re: What happened with 5.1-RELEASE? 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: Sun, 08 Jun 2003 12:23:20 -0000 On 6/7/2003 at 11:59 PM Thomas Elliott wrote: |Sorry if I rattled your cage Scott - it wasnt intentional. | |I was only saying that I found it strange that it appeared, then |dissapeared within the timespace that it took me to download the |first cd. ============= Part of the release process is to check out the the placement on, the mirroring of, and the downloading from, the main servers. This necessitates the actual release files being put on the server while the quality assurance testing is still taking place. If something is found to be 'not quite right' those files will need to be removed, the problem fixed, and the process retarted. That is, IMHO, what you experienced. Though unnerving from your point of view, it really is A Good Thing -- it shows the fastidious attention to quality that the FreeBSD teams practice. s