From owner-freebsd-current Sat Sep 26 21:15:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08213 for freebsd-current-outgoing; Sat, 26 Sep 1998 21:15:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08195 for ; Sat, 26 Sep 1998 21:14:59 -0700 (PDT) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id VAA14691; Sat, 26 Sep 1998 21:14:45 -0700 (PDT) (envelope-from Studded@dal.net) Message-ID: <360DBBB5.7D410268@dal.net> Date: Sat, 26 Sep 1998 21:14:45 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.7-STABLE-0920 i386) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: current@FreeBSD.ORG Subject: Re: Upgrade documentation (Was: Re: Make world error on -current elf) References: <1094.906862781@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > > I administer several systems that are 600 miles away, one that's 2,000. > > Source upgrades are the only path for me, and I know there's a lot of > > others in the same boat. > > There's no substitute for having someone on-site to handle a major > upgrade. Of course. That's not really the issue though. I haven't seen one message till now saying that the project doesn't plan to make the source upgrade reliable. In fact, I've seen hundreds working to make it so. I'm perfectly happy to have a backup plan ready, but it *would* be nice to have a fighting chance to make it work with a source upgrade first. > > The problem is, within the next X months, 3.0 isn't going to be > > -Current anymore, it's going to be the mainstream. IMO we need to start > > planning for this change, oh, 6 months ago or so. :) > > 3.0.0-RELEASE has also been strongly discouraged for more than the > last 6 months to any of our users who are halfway serious about > reliability, and anyone who's been ignoring our warnings does so only > at their own peril. Yes, of course. But at SOME point you do want people moving to the 3.0 branch. The process of making 3.0 into something that mere mortals can use reliably will be accelerated if some people in the middle (not developers, but not entry level users either) to migrate and shake out the bugs that the developers haven't yet. Foolishly, I took you at your word regarding the so-called beta period for 3.0-Release. Now that I know that it will be a long time before you actually want people using 3.0, I won't worry about it. > > I've already seen some of the resentment, bad feelings, etc. associated > > with this kind of shift appearing on the lists, and I expect more to > > Hmmm. I haven't seen much resentment coming from anyone but you. :-) > > Seriously, anyone getting "resentful" at this stage about the > transition is simply trying to do the wrong thing at the wrong time. > We have a release track for those who need strong shock-absorbers on > their release and it's called 2.2-STABLE. I don't think people are > taking that fact seriously enough and it's a damn shame, especially > when they start blaming *us* for their own refusal to heed the > warnings. A) You've completely misunderstood my point. B) I'm not resentful. C) You're ignoring feedback from both the users and the developers. It's too bad really, but now that I know the size of the brick wall I'll stop beating my head against it. I had hoped that given the problems of the past that you'd be open to suggestions. However it seems that you're determined to go down the same path. Just don't be surprised when you reach the same destinations. Good luck, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message