commit: 3cbde132b6b28dcaf4ae591c567b6828e4fc7688 Author: Alexey Sokolov <sokolov <AT> google <DOT> com> AuthorDate: Fri Jun 26 14:03:30 2020 +0000 Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org> CommitDate: Sun Jul 12 18:31:43 2020 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=3cbde132
keywording: Mention NATTkA Signed-off-by: Alexey Sokolov <sokolov <AT> google.com> Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org> keywording/text.xml | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/keywording/text.xml b/keywording/text.xml index 2368cf3..b151e26 100644 --- a/keywording/text.xml +++ b/keywording/text.xml @@ -245,9 +245,13 @@ the arch teams are happy for help, so long as they know what is going on. <p> In order to request stabilization of an ebuild, file a bug to the package's -maintainer (which may be yourself), and list all secondary maintainers -in the bug's CC. When the maintainers consider the ebuild to be ready for -stabilization, they will add the relevant architecture teams to the CC list. +maintainer (which may be yourself) in the Stabilization component, and list +all secondary maintainers in the bug's CC. When the maintainers consider the +ebuild to be ready for stabilization, they will add the relevant architecture +teams to the CC list. They can do it manually, or they can fill the package +list field, add the <c>CC-ARCHES</c> keyword, and let +<uri link="https://dev.gentoo.org/~mgorny/doc/nattka/";>NATTkA</uri> +automatically add arch teams to CC. That way teams can remove themselves from the list when they are done, giving a clear indication of which teams still have to stabilize a package. </p>
