| 1 |
Mark Loeser wrote: |
| 2 |
> Well, instead of putting the debate into an even larger crowd, this |
| 3 |
> enables the QA team to act in the way it sees best first. If people |
| 4 |
> believe we were wrong, then we give them the option to talk to the |
| 5 |
> council about one of our changes. Also, we aren't unwilling to hear |
| 6 |
> alternatives and we hope to work with the maintainer on these problems. |
| 7 |
|
| 8 |
As Stuart mentioned, this is not a good idea. If the maintainer |
| 9 |
disagrees with QA-made changes, the changes should be reverted until a |
| 10 |
higher-level decision is made. This mirrors FreeBSD policy [1], which |
| 11 |
seems to be working quite well for them. A particularly relevant part is |
| 12 |
this: |
| 13 |
|
| 14 |
"Any disputed change must be backed out pending resolution of the |
| 15 |
dispute if requested by a maintainer. Security related changes may |
| 16 |
override a maintainer's wishes at the Security Officer's discretion." |
| 17 |
|
| 18 |
Thanks, |
| 19 |
Donnie |
| 20 |
|
| 21 |
1. |
| 22 |
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/rules.html |
Archives