On 2008-08-25T18:58:39, "David C. Rankin"
Yes, I do appreciate that position. However, take the recent example of a user needing mod_rewrite for 10.0. That certainly seems like something that should be available and something that would make sense to use until a server upgrade could be scheduled.
The lifetime of the releases is known at the time of, well, release. One should directly schedule a server upgrade when the server is deployed; it's part of a proper lifecycle. ;-)
That is where the value lies for Novell in making at least recent past releases available.
The value to Novell/SuSE? To be honest, the value to support outdated releases for us must be below zero, ie, it is a cost. For SLES, at least we get to charge the customers for the pain and effort of doing so, but for openSUSE, it really wouldn't make sense. The community _and_ Novell benefits from keeping everyone at the tip.
Yes. We look forward to your contribution; afterall, it's only $50. ;-) Would that be credit or pay-pal ?-)
No idea. It wasn't me who introduced that number ;-)
It is a double-edge sword, but it seems like something so simple to do. Oh well, at least the issue was visited. Thanks, and do keep it in mind as things go forward. Especially in light of the new, whether-ill advised or not, "rapid-fire" release schedule. Pickup with 10.3 and go forward with a new "leave the repos up 24 mo. past eol policy" and no new effort is required and both the user base and Novell will benefit.
I personally think this would be harmful, but then, it also isn't me who makes that decision. Regards, Lars -- Teamlead Kernel, SuSE Labs, Research and Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org