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