| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi, |
| 5 |
Given the talk on last council meeting I would like this policy to be in |
| 6 |
effect over main tree: |
| 7 |
|
| 8 |
Every arch teams should stabilise OR write out reason why they can't do |
| 9 |
so to stable bug in 90 days. If any arch team fails to do so the |
| 10 |
maintainer can decide to drop their keywords to testing. Given depgraph |
| 11 |
breakages the maintainer can coordinate with the QA team to drop all |
| 12 |
reverse dependencies to testing too. |
| 13 |
Only exception from this rule are toolchain and base-system bugs, since |
| 14 |
testing-only effectively means that the arch lost stable status as whole. |
| 15 |
In order to accommodate this goals Arch Teams can generate Arch Testers |
| 16 |
which can comment on the bugs in their name, where maintainer then can |
| 17 |
act upon their comments (eg: if ARM at say that everything is ok, |
| 18 |
maintainer can stabilise it on arm...). (Come on for most stable testing |
| 19 |
you don't really need to be fully fledged Gentoo dev, but you just need |
| 20 |
the named hardware and working brain :)) |
| 21 |
|
| 22 |
Cheers |
| 23 |
|
| 24 |
Tom |
| 25 |
-----BEGIN PGP SIGNATURE----- |
| 26 |
Version: GnuPG v2.0.17 (GNU/Linux) |
| 27 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 28 |
|
| 29 |
iEYEARECAAYFAk0+thsACgkQHB6c3gNBRYfW4wCfXbctXUgKoK53Pd45QuAMgY7r |
| 30 |
Sy4AoMU6z/oS/JvUum6/29SHYsmuoQBs |
| 31 |
=LQj9 |
| 32 |
-----END PGP SIGNATURE----- |
Archives