| 1 |
> * In case of emergency, or if package maintainers refuse to cooperate, |
| 2 |
> the QA team may take action themselves to fix the problem. The QA |
| 3 |
> team does not want to override the maintainer's wishes by default, but only |
| 4 |
> wish to do so when the team finds it is in the best interest of users |
| 5 |
> and fellow developers to have the issue addressed as soon as possible. |
| 6 |
|
| 7 |
Maybe there should be something more here about dealing with maintainers |
| 8 |
who are refusing to cooperate. What if the maintainer reverts the |
| 9 |
changes that the QA team makes? |
| 10 |
|
| 11 |
> * The QA team will maintain a list of current "QA Standards" with |
| 12 |
> explanations as to why they are problems, and how to fix the problem. |
| 13 |
> The list is not meant by any means to be a comprehensive document |
| 14 |
|
| 15 |
Why isn't this list meant to be comprehensive? I know that there will be |
| 16 |
QA problems that come up that you haven't thought about yet, but it |
| 17 |
would be really really nice to have a list with all of the QA problems |
| 18 |
that could come up and how to fix them. It would help new developers |
| 19 |
avoid mistakes and it would benefit the QA team by giving them a |
| 20 |
document that they can direct devs to when there is a problem. |
| 21 |
|
| 22 |
~tcort |
| 23 |
-- |
| 24 |
gentoo-dev@g.o mailing list |
Archives