1 |
keytoaster 09/10/01 12:49:26 |
2 |
|
3 |
Modified: coordinator_guide.xml |
4 |
Log: |
5 |
Adding a sentence on STABLEREQ as requested by volkmar and craig, bug 283324 |
6 |
|
7 |
Revision Changes Path |
8 |
1.24 xml/htdocs/security/en/coordinator_guide.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/en/coordinator_guide.xml?rev=1.24&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/en/coordinator_guide.xml?rev=1.24&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/en/coordinator_guide.xml?r1=1.23&r2=1.24 |
13 |
|
14 |
Index: coordinator_guide.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/security/en/coordinator_guide.xml,v |
17 |
retrieving revision 1.23 |
18 |
retrieving revision 1.24 |
19 |
diff -u -r1.23 -r1.24 |
20 |
--- coordinator_guide.xml 9 May 2009 15:02:58 -0000 1.23 |
21 |
+++ coordinator_guide.xml 1 Oct 2009 12:49:25 -0000 1.24 |
22 |
@@ -501,13 +501,14 @@ |
23 |
<p> |
24 |
Once determined (and noted for reference on the bug) the needed KEYWORDS, |
25 |
you should Cc: arch teams and ask them to mark the ebuild stable or ~ |
26 |
-accordingly. The arches alias are archname@g.o (x86@g.o, |
27 |
-ppc@g.o...). All arches (including "unsupported" arches) must be |
28 |
-called. But note that only "supported" arches (as defined in the policy) are |
29 |
-needed before the bug can advance to [glsa] status. You should periodically |
30 |
-check for new keywords in the ebuild, as sometimes they are changed without |
31 |
-a comment in the bug. As soon as the required KEYWORDS |
32 |
-are in the bug for all supported arches, the bug enters [glsa] status. |
33 |
+accordingly. To make sure that the arch teams will pick the bug up, don't forget |
34 |
+to add "STABLEREQ" to the bug's "Keywords" field. The arches alias are |
35 |
+archname@g.o (x86@g.o, ppc@g.o...). All arches (including |
36 |
+"unsupported" arches) must be called. But note that only "supported" arches (as |
37 |
+defined in the policy) are needed before the bug can advance to [glsa] status |
38 |
+You should periodically check for new keywords in the ebuild, as sometimes they |
39 |
+are changed without a comment in the bug. As soon as the required KEYWORDS |
40 |
+are in the ebuild for all supported arches, the bug enters [glsa] status. |
41 |
</p> |
42 |
|
43 |
<p> |