On Thu, 2005-03-03 at 08:06 +0200, Pekka Savola wrote: > If c), look under "NEEDS verify" (for RHL/FC version you have) > > I assume you'd like to do c), at least initially -- it's the easiest. It is NOT anywhere near easy. Not by a long shot. Thus the reason for my speaking up. There really needs to be a list of: What was broke The proposed fix Who fixed it What should be tested > Currently there are about 16 packages waiting for one or more VERIFY > votes. It would be really useful to try help with these. VERIFYING > is really trivial if you have ever used the application in question, > and you have access to the right RHL/FC versions. I do have access, I have "verified" packages (or have I? who decides?), and I probably will continue at some level. The problem is FL needs more than just the current people and process, and what it being tested needs more rigorous (think: ISO 9001) guidelines and procedures. > > For how to do VERIFY testing, take another look at > http://www.fedoralegacy.org/wiki/index.php/QaTesting under > "Testing packages for release to updates". That URL is a start, but there is no second step after it. Everyone has read the above... where's the next chapter? > > It's really very simple! As I said; It is NOT anything close to simple, and even then it is open to too much discernment. A *kernel* has been released recently..who tested it in it's entirety? Where is the list of fixes and the checkmarks that indicate "x" was fixed by Bob and "x" was tested by Sue? -Jim P. -- fedora-legacy-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-legacy-list
