-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 28 January 2004 08:06, Pekka Savola wrote: > Btw, are all the dist versions tied together when moving from testing > to updates? I.e., can a test update be "released" before all the > arches have been tested? They are tied together. They need to move as one, so that only one announcement has to be sent, and thus avoiding confusion. > That is, because there seems to a bit of lack of support for moving > these along, could this be fast-tracked by focusing the effort on > RHL73 and doing the rest when appropriate? (Or am I looking at a wrong > problem..?) This is a real problem, and one I envisioned from the start. When I started this project, I only wanted to support RHL 7.3 and 9, but due to community influence, I've included support for 7.2 and 8.0 as well. I'm going to implement a policy that if a package receives good feedback on 7.3, and no other feedback with in 3 days, that the entire package group will be pushed to updates. Does anybody have a problem with this policy? - -- Jesse Keating RHCE (http://geek.j2solutions.net) Fedora Legacy Team (http://www.fedoralegacy.org) Mondo DevTeam (www.mondorescue.org) GPG Public Key (http://geek.j2solutions.net/jkeating.j2solutions.pub) Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAF+Gc4v2HLvE71NURAuRqAJ4+zsomhrQiCUmyE45vp59fP4sE9ACgxx6S 9eeXv1UvfiFwIWqeljOPxUc= =PowT -----END PGP SIGNATURE-----
