-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> Andi, there is a solution to this problem. That is to maintain a stable > version of cooker. Do the actual work of upgrading and fixing various What about using the three tier approach of Debian? New stuff goes in unstable, after a few weeks of qa, it goes into "stable Cooker" (that is, testing), and then the releases are "stable." As it stands, Cooker at any particular moment can be anywhere inbetween those three stages. That might allow more people to run Cooker "testing" even on production systems, as they would know while there might be bugs, it generally wouldn't ever be just plain broken. In such a situation, I'd probably opt for testing over the stable release. -Tim - -- - ---------------------------------------------------------------- Timothy R. Butler [EMAIL PROTECTED] Universal Networks http://www.uninet.info Christian Portal and Search Tool: http://www.faithtree.com Enterprise Open Source Journal: http://www.ofb.biz ================================================================ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+aA8IK37Cns9gJ0gRAjsbAJ9CVNPAIv9fvzbgh4iI5mvW4JCYBQCcC5Eo yqwPC7pYAUCFjh/i9KPSq+8= =8YM+ -----END PGP SIGNATURE-----
