Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 08 Jun 2003 08:49:01 -0600
From:      Scott Long <scottl@freebsd.org>
To:        MikeM <zlists@mgm51.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: What happened with 5.1-RELEASE?
Message-ID:  <3EE34CDD.4070407@freebsd.org>
In-Reply-To: <200306080823180609.002CD0F6@sentry.24cl.com>
References:  <20030607152936.D24263-100000@cobble.capnet.state.tx.us> <00f801c32d39$1f230380$dd8616c3@rmto90894701> <20030607215631.GB97015@laptop.lambertfam.org> <002901c32d48$7d39c8a0$dd8616c3@rmto90894701> <200306080823180609.002CD0F6@sentry.24cl.com>

next in thread | previous in thread | raw e-mail | index | archive | help
MikeM wrote:
> 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
>

No, I can tell you with 100% certainty that the release was not
pulled, restarted, reuploaded, captured by aliens, or eaten by my
cat.  Now if you all would land your black helicopters in the next
yard over, I'd appreciate it. =-)

Scott



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EE34CDD.4070407>