From owner-freebsd-stable Wed Jul 12 22: 4: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5B21937B5AB for ; Wed, 12 Jul 2000 22:03:59 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA56828; Wed, 12 Jul 2000 23:03:57 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA20978; Wed, 12 Jul 2000 23:03:47 -0600 (MDT) Message-Id: <200007130503.XAA20978@harmony.village.org> To: "Mike O'Dell" Subject: Re: problems building kernels Cc: stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 11 Jul 2000 12:12:03 EDT." <200007111612.MAA61587@servo.ccr.org> References: <200007111612.MAA61587@servo.ccr.org> Date: Wed, 12 Jul 2000 23:03:47 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007111612.MAA61587@servo.ccr.org> "Mike O'Dell" writes: : is anyone else more than a little concerned that the people who : ostensibly understand all the details can't agree as to how to : do what and when?? The people that do understand the details do agree. Those that don't understand are still arguing. It is really that simple. At least in my opinion. The upgrade path has been documented like this in UPDATING for a while now. : and this is supposed to be STABLE??? Sometimes shit happens. : give us a break, guys. you don't go changing how a kernel : gets built in a release called STABLE. We try not to. Sometimes it is necessary. : and if you didn't do that, please explain that we can just : ignore all the mail the last few days and go back to : trying to figure out why cvsup-ing the latest STABLE : release doesn't compile/run-on-SMP/etc,etc,etc Look at UPDATING. We try to keep that up to date. Sometimes it takes a couple of days to realize an entry is needed and sometimes the UPDATING maintainer (me) has a life and can't commit it the instant that something is know. : i'll restate my minority view that the FreeBSD project : *really* needs to rethink their release names and the : whole release process, rather than explaining that : we don't understand the effort's peculiar definitions : of words like "stable" This is a once in a great while situtation. Sometimes it happens. We try to avoid it, but sometimes Doodoo happens. Given the level of heat when we do this once, I think that indicates that we've been fairly successful in doing it. This is now documented in UPDATING, which everyone should read and understand before updating. It was bad that it didn't get committed until yesterday. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message