From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 87C5C158087 for ; Sat, 22 Jan 2022 21:35:36 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 861802BC01E; Sat, 22 Jan 2022 21:35:34 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CC3C22BC014 for ; Sat, 22 Jan 2022 21:35:33 +0000 (UTC) Received: from oystercatcher.gentoo.org (oystercatcher.gentoo.org [148.251.78.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 57155342E63 for ; Sat, 22 Jan 2022 21:35:32 +0000 (UTC) Received: from localhost.localdomain (localhost [IPv6:::1]) by oystercatcher.gentoo.org (Postfix) with ESMTP id BA8982AA for ; Sat, 22 Jan 2022 21:35:30 +0000 (UTC) From: "Sam James" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Sam James" Message-ID: <1642887294.e61cbdca52edcc1ff6bac20577722793703997ce.sam@gentoo> Subject: [gentoo-commits] proj/devmanual:master commit in: keywording/ X-VCS-Repository: proj/devmanual X-VCS-Files: keywording/text.xml X-VCS-Directories: keywording/ X-VCS-Committer: sam X-VCS-Committer-Name: Sam James X-VCS-Revision: e61cbdca52edcc1ff6bac20577722793703997ce X-VCS-Branch: master Date: Sat, 22 Jan 2022 21:35:30 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: 2f3e3e4e-411e-4bf7-a5e8-09e47607b609 X-Archives-Hash: 867e1dd38d9a7a12f954a957f75d250c commit: e61cbdca52edcc1ff6bac20577722793703997ce Author: Sam James gentoo org> AuthorDate: Wed Jan 12 04:26:44 2022 +0000 Commit: Sam James gentoo org> CommitDate: Sat Jan 22 21:34:54 2022 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=e61cbdca 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 gentoo.org> keywording/text.xml | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) 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