[gentoo-commits] gentoo commit in xml/htdocs/security/en: coordinator_guide.xml

["Tobias Heinlein (keytoaster)" <keytoaster@gentoo.org>]

keytoaster    09/10/01 12:49:26

  Modified:             coordinator_guide.xml
  Log:
  Adding a sentence on STABLEREQ as requested by volkmar and craig, bug 283324

Revision  Changes    Path
1.24                 xml/htdocs/security/en/coordinator_guide.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/en/coordinator_guide.xml?rev=1.24&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/en/coordinator_guide.xml?rev=1.24&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/en/coordinator_guide.xml?r1=1.23&r2=1.24

Index: coordinator_guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/security/en/coordinator_guide.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- coordinator_guide.xml	9 May 2009 15:02:58 -0000	1.23
+++ coordinator_guide.xml	1 Oct 2009 12:49:25 -0000	1.24
@@ -501,13 +501,14 @@
 <p>
 Once determined (and noted for reference on the bug) the needed KEYWORDS,
 you should Cc: arch teams and ask them to mark the ebuild stable or ~
-accordingly. The arches alias are archname@gentoo.org (x86@gentoo.org,
-ppc@gentoo.org...). All arches (including "unsupported" arches) must be
-called. But note that only "supported" arches (as defined in the policy) are
-needed before the bug can advance to [glsa] status. You should periodically
-check for new keywords in the ebuild, as sometimes they are changed without
-a comment in the bug. As soon as the required KEYWORDS
-are in the bug for all supported arches, the bug enters [glsa] status.
+accordingly. To make sure that the arch teams will pick the bug up, don't forget
+to add "STABLEREQ" to the bug's "Keywords" field. The arches alias are
+archname@gentoo.org (x86@gentoo.org, ppc@gentoo.org...). All arches (including
+"unsupported" arches) must be called. But note that only "supported" arches (as
+defined in the policy) are needed before the bug can advance to [glsa] status
+You should periodically check for new keywords in the ebuild, as sometimes they
+are changed without a comment in the bug. As soon as the required KEYWORDS
+are in the ebuild for all supported arches, the bug enters [glsa] status.
 </p>
 
 <p>