-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,
Given the talk on last council meeting I would like this policy to be in
effect over main tree:

Every arch teams should stabilise OR write out reason why they can't do
so to stable bug in 90 days. If any arch team fails to do so the
maintainer can decide to drop their keywords to testing. Given depgraph
breakages the maintainer can coordinate with the QA team to drop all
reverse dependencies to testing too.
Only exception from this rule are toolchain and base-system bugs, since
testing-only effectively means that the arch lost stable status as whole.
In order to accommodate this goals Arch Teams can generate Arch Testers
which can comment on the bugs in their name, where maintainer then can
act upon their comments (eg: if ARM at say that everything is ok,
maintainer can stabilise it on arm...). (Come on for most stable testing
you don't really need to be fully fledged Gentoo dev, but you just need
the named hardware and working brain )

Cheers

Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0+thsACgkQHB6c3gNBRYfW4wCfXbctXUgKoK 53Pd45QuAMgY7r
Sy4AoMU6z/oS/JvUum6/29SHYsmuoQBs
=LQj9
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dne 25.1.2011 12:38, Tomáš Chvátal napsal(a):
> Hi,
> Given the talk on last council meeting I would like this policy to be in
> effect over main tree:
>
> Every arch teams should stabilise OR write out reason why they can't do
> so to stable bug in 90 days. If any arch team fails to do so the
> maintainer can decide to drop their keywords to testing. Given depgraph
> breakages the maintainer can coordinate with the QA team to drop all
> reverse dependencies to testing too.
> Only exception from this rule are toolchain and base-system bugs, since
> testing-only effectively means that the arch lost stable status as whole.
> In order to accommodate this goals Arch Teams can generate Arch Testers
> which can comment on the bugs in their name, where maintainer then can
> act upon their comments (eg: if ARM at say that everything is ok,
> maintainer can stabilise it on arm...). (Come on for most stable testing
> you don't really need to be fully fledged Gentoo dev, but you just need
> the named hardware and working brain )
>
> Cheers
>
> Tom
AAnd as Mark told me I actually didn't say that i want feedback and
opinions on those two mails i just sent to this ML, so please tell us
how do you feel about it and what would you like to be done differently
These two mails (slacker arches, eapi usage) are not policies in effect
but stuff council would like to decide about and want to know the
devhood opinions.

Cheers
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0+vJMACgkQHB6c3gNBRYc4+wCeLPeysLA/xTacnofptQBbai5z
jpEAn0jyipxEV/U/IQylCmzj3IVbe3NZ
=LHQi
-----END PGP SIGNATURE-----

On 1/25/11 12:38 PM, Tomáš Chvátal wrote:
> Every arch teams should stabilise OR write out reason why they can't do
> so to stable bug in 90 days. If any arch team fails to do so the
> maintainer can decide to drop their keywords to testing. Given depgraph
> breakages the maintainer can coordinate with the QA team to drop all
> reverse dependencies to testing too.

Seconded. Reality++

Be prepared for some issues though. Sometimes maintainers don't agree
with reasons arch teams provide that block stabilizations. In those
cases, who makes the decision? My suggestion is QA.

Also, we should have someone to check for stale stabilization bugs. I'm
not sure if all reporters are able to take care of that, especially if
they have a lot of bugs open.

Paweł