On Mon, 10 Nov 2008 13:13:34 -0500
Mark Loeser <halcy0n@g.o> wrote:

> If an ebuild meets the time criteria above, and there are no
> technical issues preventing stabilization, then the maintainer MAY
[...] mark that ebuild as stable on every keyworded arch (that has a
stable keyword).

> If an ebuild meets the time criteria above, but there is a technical
> issue preventing stabilization, and there are no outstanding security
> issues,
[...] the maintainer MUST NOT mark the ebuild stable without the
approval of the arch team.

If technical issues arise after an ebuild is stabilized automatically,
the arch team MAY revert the ebuild to ~arch if another ebuild with a
stable keyword is still available or restore the previous stable ebuild
to the tree if not, until such time that the issue is resolved, or
stabilize a later versioned ebuild that does not exhibit the issue at
the maintainer's approval.

The maintainer MUST NOT NEVER EVER NOT EVEN A LITTLE BIT remove the
latest stable ebuild of an arch without the approval of the arch team or
he/she will be fed to the Galrog.


and s/30 days/90 days/g.


-- 
gcc-porting,                                      by design, by neglect
treecleaner,                              for a fact or just for effect
wxwidgets @ gentoo     EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662