Date: Thu, 5 Jun 2008 10:35:45 +1000 From: Edwin Groothuis <edwin@mavetju.org> To: Jo Rhett <jrhett@netconsonance.com> Cc: FreeBSD Stable <freebsd-stable@FreeBSD.org>, Doug Barton <dougb@FreeBSD.org>, Steven Hartland <killing@multiplay.co.uk> Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 Message-ID: <20080605003545.GP89632@k7.mavetju> In-Reply-To: <FB44670E-6F56-44BE-ADC4-23126420FAD8@netconsonance.com> References: <458FE12C-AE4D-48F9-8193-4663079CEEF8@netconsonance.com> <84EBEA5D3A1F47E79E8E12C4CF4D0314@multiplay.co.uk> <FB44670E-6F56-44BE-ADC4-23126420FAD8@netconsonance.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 04, 2008 at 05:24:42PM -0700, Jo Rhett wrote: > On Jun 4, 2008, at 5:17 PM, Steven Hartland wrote: > >I wouldn't be surprised if these are not new bugs, just something > >that others have noticed later than 6.2 and I'd suggest you actually > >try 6.3 to see if they are in fact an issue for you. > > I don't have the resources to load up the systems enough to find these > problems sitting on my desk. And I can't risk production resources > for problems known and reported on the *EXACT* same hardware. > > "oh but it won't happen to me" isn't a useful methodology in a > production environment. > > I mean, seriously, I know the majority of you are happy rebooting your > systems 5x daily to run the latest. I'll do that with my home system, > no problem. But I can't do this in a production environment. Use the eat-your-own-food approach (while not knowing what the 500 systems do): Make sure you use the same hardware and software as what is in production. Upgrade it first, run it for two weeks. If it doesn't, fallback and see where it went wrong. If it all works fine after two weeks, roll it out. Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080605003545.GP89632>