1 |
On Mon, 10 Nov 2008 13:13:34 -0500 |
2 |
Mark Loeser <halcy0n@g.o> wrote: |
3 |
|
4 |
> If an ebuild meets the time criteria above, and there are no |
5 |
> technical issues preventing stabilization, then the maintainer MAY |
6 |
[...] mark that ebuild as stable on every keyworded arch (that has a |
7 |
stable keyword). |
8 |
|
9 |
> If an ebuild meets the time criteria above, but there is a technical |
10 |
> issue preventing stabilization, and there are no outstanding security |
11 |
> issues, |
12 |
[...] the maintainer MUST NOT mark the ebuild stable without the |
13 |
approval of the arch team. |
14 |
|
15 |
If technical issues arise after an ebuild is stabilized automatically, |
16 |
the arch team MAY revert the ebuild to ~arch if another ebuild with a |
17 |
stable keyword is still available or restore the previous stable ebuild |
18 |
to the tree if not, until such time that the issue is resolved, or |
19 |
stabilize a later versioned ebuild that does not exhibit the issue at |
20 |
the maintainer's approval. |
21 |
|
22 |
The maintainer MUST NOT NEVER EVER NOT EVEN A LITTLE BIT remove the |
23 |
latest stable ebuild of an arch without the approval of the arch team or |
24 |
he/she will be fed to the Galrog. |
25 |
|
26 |
|
27 |
and s/30 days/90 days/g. |
28 |
|
29 |
|
30 |
-- |
31 |
gcc-porting, by design, by neglect |
32 |
treecleaner, for a fact or just for effect |
33 |
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |