From owner-freebsd-stable@FreeBSD.ORG Wed Jun 4 18:00:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38D081065670 for ; Wed, 4 Jun 2008 18:00:47 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.freebsd.org (Postfix) with ESMTP id B2CF68FC1B for ; Wed, 4 Jun 2008 18:00:46 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 21001 invoked by uid 399); 4 Jun 2008 18:14:01 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 4 Jun 2008 18:14:01 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4846D849.2090005@FreeBSD.org> Date: Wed, 04 Jun 2008 11:00:41 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.14 (X11/20080525) MIME-Version: 1.0 To: Jo Rhett References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> In-Reply-To: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> X-Enigmail-Version: 0.95.6 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2008 18:00:47 -0000 Jo Rhett wrote: > Okay, I totally understand that FreeBSD wants people to upgrade from 6.2 > to 6.3. It isn't that we want people to upgrade, it's that we are trying to be realistic regarding what we have the resources to support. > But given that 6.3 is still experiencing bugs with things that > are working fine and stable in 6.2, this is a pretty hard case to make. I admit to not having been following 6.x too closely, but are these things that have been reported, or problems you're having personally? > This is also a fairly significant investment in terms of time and money > for any business to handle this ugprade. Having an upgrade path is something every operation needs. "Set it and forget it" isn't a viable strategy in the current culture where 0-day vulnerabilities are becoming increasingly common. hth, Doug -- This .signature sanitized for your protection