From owner-freebsd-current Tue Sep 3 19:04:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA15257 for current-outgoing; Tue, 3 Sep 1996 19:04:47 -0700 (PDT) Received: from VX23.CC.MONASH.EDU.AU (vx23.cc.monash.edu.au [130.194.1.23]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA15246 for ; Tue, 3 Sep 1996 19:04:41 -0700 (PDT) Received: from moa.cc.monash.edu.au (george@moa.cc.monash.edu.au) by vaxc.cc.monash.edu.au (PMDF V5.0-6 #16291) id <01I92W7CHXJI984THU@vaxc.cc.monash.edu.au> for current@FreeBSD.org; Wed, 04 Sep 1996 11:58:19 +1000 Received: (george@localhost) by moa.cc.monash.edu.au (8.6.10/8.6.4) id LAA05909 for current@FreeBSD.org; Wed, 04 Sep 1996 11:58:17 +1000 Date: Wed, 04 Sep 1996 11:58:17 +1000 From: George Scott Subject: Re: Latest Current build failure To: current@FreeBSD.org Message-id: <199609040158.LAA05909@moa.cc.monash.edu.au> Content-transfer-encoding: 7BIT Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Hell, the concept of "production level" doesn't even make sense when > discussing what's essentially a live snapshot of the engineering > team's working sources and, if anything, the real problem here is that > the WRONG PEOPLE are running -current! I think that part of the problem might be that the name is a little bit misleading. When I first started looking at FreeBSD and heard about CURRENT I had an image in my mind of the current release, ie, what I later discovered was called -RELEASE. A name like DEVEL might have been less confusing. I'm not suggesting that the name be changed, just trying to explain a phenomenon. Maybe the solution to the problem would be better advertising (ie, where -CURRENT is mentioned make it clear that it is development code). George. -- George Scott George.Scott@cc.monash.edu.au Systems Programmer, Caulfield Computer Centre, Monash University