1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Dne 25.1.2011 12:38, Tomáš Chvátal napsal(a): |
5 |
> Hi, |
6 |
> Given the talk on last council meeting I would like this policy to be in |
7 |
> effect over main tree: |
8 |
> |
9 |
> Every arch teams should stabilise OR write out reason why they can't do |
10 |
> so to stable bug in 90 days. If any arch team fails to do so the |
11 |
> maintainer can decide to drop their keywords to testing. Given depgraph |
12 |
> breakages the maintainer can coordinate with the QA team to drop all |
13 |
> reverse dependencies to testing too. |
14 |
> Only exception from this rule are toolchain and base-system bugs, since |
15 |
> testing-only effectively means that the arch lost stable status as whole. |
16 |
> In order to accommodate this goals Arch Teams can generate Arch Testers |
17 |
> which can comment on the bugs in their name, where maintainer then can |
18 |
> act upon their comments (eg: if ARM at say that everything is ok, |
19 |
> maintainer can stabilise it on arm...). (Come on for most stable testing |
20 |
> you don't really need to be fully fledged Gentoo dev, but you just need |
21 |
> the named hardware and working brain :)) |
22 |
> |
23 |
> Cheers |
24 |
> |
25 |
> Tom |
26 |
AAnd as Mark told me I actually didn't say that i want feedback and |
27 |
opinions on those two mails i just sent to this ML, so please tell us |
28 |
how do you feel about it and what would you like to be done differently :) |
29 |
These two mails (slacker arches, eapi usage) are not policies in effect |
30 |
but stuff council would like to decide about and want to know the |
31 |
devhood opinions. |
32 |
|
33 |
Cheers |
34 |
Tom |
35 |
-----BEGIN PGP SIGNATURE----- |
36 |
Version: GnuPG v2.0.17 (GNU/Linux) |
37 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
38 |
|
39 |
iEYEARECAAYFAk0+vJMACgkQHB6c3gNBRYc4+wCeLPeysLA/xTacnofptQBbai5z |
40 |
jpEAn0jyipxEV/U/IQylCmzj3IVbe3NZ |
41 |
=LHQi |
42 |
-----END PGP SIGNATURE----- |