From owner-freebsd-current  Fri May  2 21:50:18 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA12116
          for current-outgoing; Fri, 2 May 1997 21:50:18 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA12093
          for <current@freebsd.org>; Fri, 2 May 1997 21:50:15 -0700 (PDT)
Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id VAA15682; Fri, 2 May 1997 21:50:40 -0700 (PDT)
To: John Polstra <jdp@polstra.com>
cc: current@freebsd.org
Subject: Re: -current build is now broken.. 
In-reply-to: Your message of "Fri, 02 May 1997 08:54:10 PDT."
             <199705021554.IAA21290@austin.polstra.com> 
Date: Fri, 02 May 1997 21:50:39 -0700
Message-ID: <15680.862635039@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> But it seems that you are asking most developers themselves to
> acquire exactly those resources, or to have one of the few (3?)
> release engineers review any changes to *.mk, /usr/src/Makefile,
> include files, libraries, compiler, assembler, linker, ... creating
> a very narrow bottleneck indeed.  Wouldn't it make more sense to
> solicit whatever contributions are needed to put the required
> resources (3 disk drives total?) into the hands of the few release
> engineers, so that they can have release building machines running
> -current?

Hmmmm.  Well, since it seems like this is going to become the defacto
state of affairs anyway, no matter how much I yell and scream about
wider release testing, I suppose I have little choice. ;-)

						Jordan