From owner-freebsd-hackers  Wed Oct 16 13:35:42 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA03400
          for hackers-outgoing; Wed, 16 Oct 1996 13:35:42 -0700 (PDT)
Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA03384
          for <freebsd-hackers@freebsd.org>; Wed, 16 Oct 1996 13:35:34 -0700 (PDT)
Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id PAA28535; Wed, 16 Oct 1996 15:34:22 -0500
From: Joe Greco <jgreco@brasil.moneng.mei.com>
Message-Id: <199610162034.PAA28535@brasil.moneng.mei.com>
Subject: Re: IP bugs in FreeBSD 2.1.5
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Wed, 16 Oct 1996 15:34:21 -0500 (CDT)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <29738.845497279@time.cdrom.com> from "Jordan K. Hubbard" at Oct 16, 96 01:21:19 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > Jordan, I don't know how you think bugs get found, but in my experience
> > they get found by people giving the code a workout.  In order to get
> > a stable "R" release, this means that the code has to be given a workout
> > BEFORE the release - during the "A/B/G" phases.
> 
> And I guess I don't know what you consider "production" systems, but I
> would still never bring such a system into a true production
> environment, period..  I would test it on another machine using
> *simulated* load or some collection of my users who were in turn
> explictly BETA customers themselves, but anything more than this and
> you're running plain off the rails and NOT doing what I try to
> recommend that FreeBSD's users do (e.g. "don't run pre-releases on
> your production hardware!").
> 
> That's my story and I'm sticking with it.

I generally engineer redundancy into my systems.  If I feel that I can
afford to risk losing one system when a backup with a high confidence 
level is available, wouldn't you rather see me test the release on a 
production system where it will be applied to real world stresses?

It is not exactly playing Russian Roulette, ya know.  :-)  I'd be much
more hesitant to do it with Linux.

Since I am ultimately answerable to myself with respect to my systems 
and operations, if I feel comfortable running a pre-release on a system,
I promise not to blame you for any problems discovered while doing so.
I might certainly submit some PR's, though, and that should be what a
pre-release period is all about.

Okay?  :-)

... JG