From e61cbdca52edcc1ff6bac20577722793703997ce Mon Sep 17 00:00:00 2001 From: Sam James Date: Wed, 12 Jan 2022 04:26:44 +0000 Subject: keywording: add explanatory text on maintainer obligations Inspired partly by a discussion on a GitHub pull request [0]. [0] https://github.com/gentoo/gentoo/pull/23735 Signed-off-by: Sam James --- keywording/text.xml | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) (limited to 'keywording') diff --git a/keywording/text.xml b/keywording/text.xml index cc10166..ed6b6d1 100644 --- a/keywording/text.xml +++ b/keywording/text.xml @@ -243,6 +243,29 @@ to do this. Moving from <c>~arch</c> to <c>arch</c> +

+If a package has stable keywords, maintainers should regularly (subject to the +rules below) file stabilization bugs for their packages, ideally approximately +every 30 days after a new version is added. If a bug report for stabilization +is filed by somebody else, the maintainer should respond with an +acknowledgement ("ACK") if the ebuild is ready, and a negative +acknowledgement ("NAK") if not. +

+ +

+Previous stable keywords should not be dropped without good cause and it is +courteous to ping members of the relevant arch team first. Maintainers must not +drop stable keywords simply because they don't have access to a platform: this +is what Gentoo's arch teams are here for. +

+ +

+By convention, these bugs are assigned to package maintainers, but the only +action expected from maintainers is to acknowledge or reject the +stabilization rather than carry out additional testing on each required +architecture themselves. +

+

Stabilization, i.e., moving an ebuild from ~arch ("testing") to arch ("stable"), is done by the relevant architecture teams. If you have -- cgit v1.2.3-65-gdbad