-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jesse Keating wrote: > > If I'm not mistaken, the timeout period starts when there is a package > for updates testing. We can't get to the updates testing package phase > w/out somebody doing the first level QA which includes making sure the > patch uses is a known good patch from at least some other vendor. So > the plot to root all Legacy systems is going to have to start further up > the food chain. > OK, Maybe we (Fedora Legacy) need to define the process of getting a package from bug report (or SA) to QA released state, and stop arguing who is at fault or how to bypass QA. If everyone knows the process and follows it we all can benefit... Maybe, its time I started witting something! A document on the whole process for everyone to review and agree upon... unless something like this already exists... which I've never seen. Thanks, James Kosin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD8hQokNLDmnu1kSkRAu1nAJwJq9OK49o7lHySze7/YdD946z/vQCfaGg8 zAIWK7orCaOp/IYyu63R0Jg= =b0lD -----END PGP SIGNATURE----- -- Scanned by ClamAV - http://www.clamav.net -- fedora-legacy-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-legacy-list
