On Tue, Dec 24, 2002 at 04:17:55AM +0800, Tim Kehres wrote: > I'll probably regret replying to this by morning, but let's give it a > try.... :-)
So I'll take a stab at it before morning :-) > There are two issues here - how long to support the old releases, and how > often to update. Given the cost of acquiring updates (free given a > reasonable net connection), limiting the time to support a release seems > reasonable to me. You've actually missed a very significant cost and that's the testing and migration from release to release. Getting 8.0 is easy. Migrating all the current web-based apps from 1.3.x to 2.0 isn't. Similarly with everthing else. My job consists of about 95% planning and 5% action. When you've got servers with hundreds of accounts, you can't just throw an upgrade in and hope nobody notices. As I said before, this isn't my home system we're talking about. The sign on my door (when I had a door :-)) said "when downtime is not an option". This applies to all the OSs my group supports but if I take a day to upgrade each system twice per year, I've blown a month. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
