From owner-freebsd-stable@FreeBSD.ORG Thu Jun 5 05:33:32 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 C52A9106566B for ; Thu, 5 Jun 2008 05:33:32 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4]) by mx1.freebsd.org (Postfix) with ESMTP id AA3BF8FC1E for ; Thu, 5 Jun 2008 05:33:32 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from [172.16.12.8] (covad-jrhett.meer.net [209.157.140.144]) (authenticated bits=0) by mail.netconsonance.com (8.14.1/8.14.1) with ESMTP id m555XUwW079624 for ; Wed, 4 Jun 2008 22:33:30 -0700 (PDT) (envelope-from jrhett@netconsonance.com) X-Virus-Scanned: amavisd-new at netconsonance.com X-Spam-Flag: NO X-Spam-Score: -3.649 X-Spam-Level: X-Spam-Status: No, score=-3.649 tagged_above=-999 required=3.5 tests=[ALL_TRUSTED=-1.44, AWL=-2.209] Message-Id: From: Jo Rhett To: FreeBSD Stable In-Reply-To: <484736E0.6090004@samsco.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 4 Jun 2008 22:33:30 -0700 References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <4846E637.9080101@samsco.org> <48472DB6.5030909@samsco.org> <6010676B-91B0-4AF8-ACF8-039A59B29331@netconsonance.com> <484736E0.6090004@samsco.org> X-Mailer: Apple Mail (2.919.2) Subject: CLARITY 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: Thu, 05 Jun 2008 05:33:32 -0000 I'm going to be offline for a week starting now, so please don't read my lack of answers as anything other than "out of town". Sorry. For clarity: I'm not asking for anyone to fix anything. I honestly believe most developers are addressing problems as fast as they can. I'd help them in any way I could. I am suggesting that given that the current bug list for 6.3-RELEASE is both (a) too large and (b) breaks things that work fine in 6.2 ... that I think pushing 6.2 (the real stable release) into EoL is a bit rushed. I sympathize with the development costs of maintaining old versions. Again, I will help in any way I can. On my return next week I would happily build and provide 6.3-RELEASE systems for any developer who needs a test environment for reported bugs that affect hardware I have in my possession. Free boxes, free bandwidth, power, etc. No problem. Free my time in whatever way I can help. But until such time as the current bug list for 6.3 hardware reduces to somewhere less than 100% likelyhood of experiencing failures after an upgrade, there's just no way I can take our production environment forward. Going "bravely forward" to guaranteed failure isn't a great way to enjoy your job :-( Which means I'll be doing our security patches by hand. Because it may be time intensive, but it's less likely to cause a production failure. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness