-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 R Hill wrote: [snip] | How about the ATs cc the maintainer on the bug they | file to get the pkg bumped to stable, and giving them a period of time | (48 hours? a week?) in which to raise any objections. Of course the AT's | would still have the power to go over the maintainers head in case of | an emergency - but only if the maintainer can't be reached, or can't do it | themselves for whatever reason, or is just being a big dink. You are missing the whole point of an AT. ATs have no inherit power, they arn't even officialy gentoo people(yet). All an AT can do is comment on the particular piece of software in question.
An arch team(not AT) could disregard the package maintainers thoughts and move said package to stable before the maintainer does on his arch. ~ However, this should be the exception, and not the rule. Realisticly, if people stop being asses and work together, then a consensus should allways be possible. Only when people don't work together does a situation like this arise. The formation of a x86 arch team should be viewed as additional help to maintainers who use x86, as well as act as the group that keywords for x86 for those devs who don't use x86 as their arch. - -- ======================================================= Mike Doty [EMAIL PROTECTED] Gentoo/AMD64 Strategic Lead PGP Key: 0xA797C7A7 Gentoo Developer Relations ~ ===GPG Fingerprint=== ~ 0094 7F06 913E 78D6 F1BB 06BA D0AD D125 A797 C7A7 ======================================================= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDHHoK0K3RJaeXx6cRAppYAJ4pOihol4L6PEG4FOLF9d3uXjfJdACfRYH8 oVVySxBKfND2PBp450TiMAs= =qm7h -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
