Date: Sun, 22 Feb 1998 10:35:19 +1030 From: Greg Lehey <grog@lemis.com> To: Richard Wackerbarth <rkw@dataplex.net> Cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. Message-ID: <19980222103519.61452@freebie.lemis.com> In-Reply-To: <l03130305b11461699b54@[208.2.87.4]>; from Richard Wackerbarth on Sat, Feb 21, 1998 at 05:00:24AM -0600 References: <23061.888029515@time.cdrom.com>; <199802210245.NAA06439@cimlogic.com.au> <23061.888029515@time.cdrom.com> <19980221143803.31160@freebie.lemis.com> <l03130305b11461699b54@[208.2.87.4]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 21 February 1998 at 5:00:24 -0600, Richard Wackerbarth wrote: > At 10:08 PM -0600 2/20/98, Greg Lehey wrote: >> On Fri, 20 February 1998 at 18:51:55 -0800, Jordan K. Hubbard wrote: >>>> Jordan K. Hubbard wrote: >>>>> Yeah, no kidding. Since nobody seems to be build testing their >>>>> changes anymore I guess I'll just... > >> There's a delicate balance here: >> >> - If people commit only perfect code, the result is -STABLE, not >> -CURRENT. While that doesn't sound bad in itself, it means >> significant delays to any commit. >> >> - If people commit only code which breaks a 'make world', nobody will >> ever get -CURRENT installed. Even if it only happens 50% of the >> time, it will frustate a large number of users to the point where >> they can't be bothered any more. >> >> The problem with both of these extremes... > >> You could say "John should test his changes better before commiting >> them". But that's not always possible. The bugs don't break things >> for him. -CURRENT's there exactly for that. > > Here, I disagree. "Jane" may not be able to test ALL cases. However, > she SHOULD have already tested at least one. I think you misunderstood my message. Presumably your "Jane" is fictitious. As John pointed out, he's not. He also pointed out one reason why his test installation didn't cover every possibility. It's great to hear that he can now perform more tests than previously. But he'll never be able to test everything, and the virtual memory system pervades the whole operating system. The result: he'll commit more code which breaks. This isn't to belittle John. On the contrary, he's using -CURRENT for the purpose for which it is intended: to give better testing for code which works for him. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980222103519.61452>