From owner-freebsd-current Sun Sep 1 23:23:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA14919 for current-outgoing; Sun, 1 Sep 1996 23:23:56 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA14914 for ; Sun, 1 Sep 1996 23:23:53 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id BAA08689; Mon, 2 Sep 1996 01:21:59 -0500 (EST) From: "John S. Dyson" Message-Id: <199609020621.BAA08689@dyson.iquest.net> Subject: Re: Current build failure To: louie@TransSys.COM (Louis A. Mamakos) Date: Mon, 2 Sep 1996 01:21:57 -0500 (EST) Cc: michaelh@cet.co.jp, kimc@w8hd.org, current@FreeBSD.org In-Reply-To: <199609020539.BAA04383@whizzo.transsys.com> from "Louis A. Mamakos" at Sep 2, 96 01:39:27 am Reply-To: dyson@FreeBSD.org X-Mailer: ELM [version 2.4 PL24 ME8] 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 > > > > Keep supping and making (once a week or once a day), current is often not > > buildable. > > Ah, I thought that while current was on the bleeding edge, the code > should certainly at least compile before it's checked in! Hard to > imagine any good reason why it wouldn't complile, short of problems in > the build environment. > Actually, I think that the goal is to make sure that -current is buildable. However, it is on the "edge", and it is probably best not to condemn a developer for a mistake (or also likely, a tree that is internally inconsistant due to windows during the commit/download process.) It is exceptionally difficult to test some kinds of changes given limited resources (everything from subtile kernel changes to certain build environment changes.) Actually, since FreeBSD and it's ilk are volunteer efforts, we are fortunate that there are so many dedicated individuals spending their personal time on these projects!!! Not only that, but many of the developers don't have multiple machines to run carefully constructed tests. I believe that everyone on the project is trying to do the best job that they can, given their resources... But, again, I believe that it is pretty clear that we should be checking in code that each of us has tested as well as we can. Mess-ups do happen, and I am sure that each developer will correct the bugs they cause as quickly as possible. John