-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 08 December 2003 12:37 am, John Davis wrote: > If there is a moving target for my server class machine(s), then I, as > an IT adminstrator, must evaluate the new version, check what has > changed, make sure it still works, and then apply all of that to each > and every one of my applicable servers. (i.e, a ton of work) > > The goal here is to minimize that process. If I, as an IT administrator, > know that the only things changing when my packages update are either > security fixes or critical updates, my workload is reduced considerably, > and I rest easy. Then one would want to lock to some kind of "feature frozen" version which could be then updated for fixes. There's no reason for all servers everywhere to lock on an old version of a server, only the current stable version when they were installed. - -- Luke-Jr Developer, Gentoo Linux http://www.gentoo.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/09fNZl/BHdU+lYMRAjT3AJ4+H0oI/YIFjdu6cp1ZXdzYhQ1jQACfQ010 eW1bYcWewoSulFwdKZFXSt8= =x7S0 -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
