From owner-freebsd-hackers Wed Aug 30 13:51:43 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id NAA00354 for hackers-outgoing; Wed, 30 Aug 1995 13:51:43 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id NAA00345 for ; Wed, 30 Aug 1995 13:51:31 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id NAA09467; Wed, 30 Aug 1995 13:41:21 -0700 From: "Rodney W. Grimes" Message-Id: <199508302041.NAA09467@gndrsh.aac.dev.com> Subject: Re: /etc/disktab and stuff To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 30 Aug 1995 13:41:21 -0700 (PDT) Cc: jdl@chromatic.com, hackers@freebsd.org In-Reply-To: <6125.809813521@time.cdrom.com> from "Jordan K. Hubbard" at Aug 30, 95 01:12:01 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2207 Sender: hackers-owner@freebsd.org Precedence: bulk > > > To generalize and maybe speak (incorrectly?) for others, I think this > > area of sysadmin scares people. I know I was scared by it because I use > > it so infrequently, know so little about it, and it's so potentially > > "catastrophic" when things go wrong. Handholding during this stage can > > be very useful and very important. > > I agree. The 2.0.5 install was, to go further, rather fundamentally > flawed in that it was an "all or nothing" kinda bet. You jumped in > and went all the way or you didn't bother jumping in. 2.1 will be > substantially different in that regard. I am afraid 72 hours before beta goes out the door is _not_ the time to come up with ``substatially different'' functionality. Take off your engineering hat, put on the shipping hat and kick the thing out the door. I have not seen the code commits to make sysinstall ``substatially different'' and the next 72 hours is not the time to make it that way. For the prior 2 releases the #1 gatting issues has been install tools, well, your not done again, just go with what is there, document the known bugs and short commings, write an appology for all the things promised that did not make it, and SHIP. Perhaps if you where to spend some time in other shoes of those who have to deal with product shipment on a day in day out business you might get a better appreciation for what it means to ``get it out the door on time''. And that this often means getting it out the door far from the ideal product you had in mind. It was agreed that at the 2.1 branch point there we be no _NEW_ functinality in 2.1 over 2.0.5, so far I have seen slow creep coming in, and am now going to yell FOUL as load as I can. You and David can override me, that is a majority vote of the release team, but right now I am standing here looking at the 4th day of failed make worlds in -stable and am starting to get rather PISSED about it. The delta rate of code change is suppose to go to near _ZERO_ before the beta goes out, not climb to a record high the day before! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD