From owner-freebsd-current Tue Sep 3 12:04:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA19042 for current-outgoing; Tue, 3 Sep 1996 12:04:27 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA19035 for ; Tue, 3 Sep 1996 12:04:23 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA04818; Tue, 3 Sep 1996 12:02:35 -0700 From: Terry Lambert Message-Id: <199609031902.MAA04818@phaeton.artisoft.com> Subject: Re: Latest Current build failure To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 3 Sep 1996 12:02:35 -0700 (MST) Cc: rkw@dataplex.net, current@FreeBSD.org In-Reply-To: <9251.841752628@time.cdrom.com> from "Jordan K. Hubbard" at Sep 3, 96 05:10:28 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > The simple fact of the matter is that there is no fool-proof method > for preventing programmer errors, and providing on-the-fly access to > the development sources opens us far wider than *any* commercial UN*X > vendor to having "customers" trip over problems when they occur. There are writer locks which you are not permitted to release until a full build succeeds. But of course, that's shot down each time it is brought up. At Novell, using CVS with a reader/writer lock front end, we were able to keep a project with 18+ engineers hacking on it 8-12 hours a day buildable for every night but 5 for a period of 8 months. Further, we did it on three machine architectures. This is a heck of a lot more variance than is experienced by the FreeBSD project. It is nothing more than a matter of self-discipline combined with some simple tool changes. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.