-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dne 28.12.2009 03:43, Richard Freeman napsal(a): > > Could this include documenting QA policies a bit better? Some are > documented in scattered docs, some are in the ebuild quiz answers (which > of course no two developers have the exact same answers to, and they > aren't anywhere you can point to for reference), and many are learned > when QA files a bug on a package one maintains. > > It would be really nice to just have a list somewhere that we could > periodically look at and refresh our memories against. Plus, some > policies aren't always obvious or can be misinterpreted. > > Don't get me wrong - the QA team is doing a great job and I love Diego's > work on the tinderbox. I've had a bug or two filed by them, and I've > found that they've only been helpful when somebody actually bothers to > try to resolve them. >
Yeah that is the weak point. We need to write for each policy what it does and why we enforce it (probably also common approach to fix). And we should ENFORCE it, not just fill bugs about it, because mostly people tend to ignore that things. Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAks4lT4ACgkQHB6c3gNBRYfS+QCfdw7ler6i8xGPufZnNsQjNV9m bBYAoKLKekHRe6SShSNcU7jHIEZiYrCw =9y3A -----END PGP SIGNATURE-----
