Date: Tue, 3 Sep 1996 12:02:35 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: rkw@dataplex.net, current@FreeBSD.org Subject: Re: Latest Current build failure Message-ID: <199609031902.MAA04818@phaeton.artisoft.com> In-Reply-To: <9251.841752628@time.cdrom.com> from "Jordan K. Hubbard" at Sep 3, 96 05:10:28 am
next in thread | previous in thread | raw e-mail | index | archive | help
> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609031902.MAA04818>