| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hello all, |
| 5 |
The new QA team has completed its first meeting, and so I would like |
| 6 |
to announce policy changes agreed upon during the meeting which are |
| 7 |
relevant to the developer community. In the future, when a meeting |
| 8 |
results in changed or amended policy, we will notify the community via |
| 9 |
- -dev and -dev-announce, so there will probably be a summary email like |
| 10 |
this coming out about once a month. Changes to policy from this meeting: |
| 11 |
|
| 12 |
- -USE-controlled optional RDEPENDs policy clarified to say that those |
| 13 |
dependencies are not allowed, but QA will grant exceptions for certain |
| 14 |
circumstances (such as a package not working unless one of a set of |
| 15 |
optional deps is installed) |
| 16 |
|
| 17 |
- -The QA team policymaking workflow will look like the following: |
| 18 |
* User/dev/team member brings us an issue |
| 19 |
* Team investigates |
| 20 |
* Team discusses at the next meeting |
| 21 |
** If the person is violating policy, we inform them of that and |
| 22 |
request that they stop violating policy |
| 23 |
** If the existing policy is unclear, we update it |
| 24 |
** If there is no existing policy, make one |
| 25 |
If we think a developer's actions are causing problems, we may ask |
| 26 |
them to stop/undo pending discussion by the QA team at the next meeting. |
| 27 |
|
| 28 |
- -Rules for the QA team editing peoples' packages: |
| 29 |
*For trivial fixes, such as repoman errors, we fix the issue and send |
| 30 |
the developer a friendly reminder |
| 31 |
*For large but non-critical fixes, we open a bug, wait 2 weeks, and if |
| 32 |
it is not fixed within that time frame we make the change. |
| 33 |
*For critical fixes, such as a problem that breaks the tree or a |
| 34 |
package, we fix the issue and send the developer a notice about our change |
| 35 |
|
| 36 |
- -The QA team will communicate changes to policy via emails to |
| 37 |
gentoo-dev and gentoo-dev-announce and by updating the QA policy page |
| 38 |
on the Gentoo Wiki. |
| 39 |
|
| 40 |
For anyone interested, the summary of the meeting can be found at |
| 41 |
https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Meeting_Summaries |
| 42 |
and the current set of QA policies can be found at |
| 43 |
https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Policies. If |
| 44 |
you have any questions or concerns about these policies, feel free to |
| 45 |
discuss them with us in #gentoo-qa or by emailing qa@g.o. |
| 46 |
|
| 47 |
Chris Reffett |
| 48 |
Gentoo QA Lead |
| 49 |
-----BEGIN PGP SIGNATURE----- |
| 50 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 51 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 52 |
|
| 53 |
iKYEARECAGYFAlLp51VfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl |
| 54 |
bnBncC5maWZ0aGhvcnNlbWFuLm5ldEM2NzU5RjUyMDczREJDQkVDQTBDRkE1NERC |
| 55 |
Nzk1QThBNDI2MTgzNTQACgkQ23laikJhg1R6zwCfXY0q7Ig3d40Xq2hScLcT4Hm6 |
| 56 |
zE8AoJfIWsuV9yAKdsuxwB6JSDr8KbZY |
| 57 |
=sheY |
| 58 |
-----END PGP SIGNATURE----- |
Archives