Thomas Cort wrote:
* The QA team will maintain a list of current "QA Standards" with
explanations as to why they are problems, and how to fix the problem.
The list is not meant by any means to be a comprehensive document
Why isn't this list meant to be comprehensive? I know that there will be
QA problems that come up that you haven't thought about yet, but it
would be really really nice to have a list with all of the QA problems
that could come up and how to fix them. It would help new developers
avoid mistakes and it would benefit the QA team by giving them a
document that they can direct devs to when there is a problem.
~tcort
Is a complete list of QA problems possible? I don't think that would
necessarily be a finite list.
-tercel
--
gentoo-dev@gentoo.org mailing list
