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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 627F51382C5 for ; Wed, 7 Apr 2021 17:35:34 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A0475E09BE; Wed, 7 Apr 2021 17:35:32 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 88EF8E09BE for ; Wed, 7 Apr 2021 17:35:32 +0000 (UTC) Received: from oystercatcher.gentoo.org (unknown [IPv6:2a01:4f8:202:4333:225:90ff:fed9:fc84]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 17903335D89 for ; Wed, 7 Apr 2021 17:35:31 +0000 (UTC) Received: from localhost.localdomain (localhost [IPv6:::1]) by oystercatcher.gentoo.org (Postfix) with ESMTP id 907EE64D for ; Wed, 7 Apr 2021 17:35:28 +0000 (UTC) From: "Ulrich Müller" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Ulrich Müller" Message-ID: <1617816909.acfc48b80657c6221e1a4000ec046c65cd72fcc6.ulm@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: ulm X-VCS-Committer-Name: Ulrich Müller X-VCS-Revision: acfc48b80657c6221e1a4000ec046c65cd72fcc6 X-VCS-Branch: master Date: Wed, 7 Apr 2021 17:35:28 +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: b43746cb-54ec-452f-88de-1b0a06d8cddb X-Archives-Hash: 58582013a4a7750db1dc42167aefbd81 commit: acfc48b80657c6221e1a4000ec046c65cd72fcc6 Author: Sam James gentoo org> AuthorDate: Sun Mar 21 05:18:18 2021 +0000 Commit: Ulrich Müller gentoo org> CommitDate: Wed Apr 7 17:35:09 2021 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=acfc48b8 keywording: call ~arch ("testing") and arch ("stable") Signed-off-by: Sam James gentoo.org> Signed-off-by: Ulrich Müller gentoo.org> keywording/text.xml | 27 ++++++++++++++------------- 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/keywording/text.xml b/keywording/text.xml index 6d7c394..0f08c7e 100644 --- a/keywording/text.xml +++ b/keywording/text.xml @@ -38,14 +38,14 @@ The different levels of keyword are:
- arch (x86, ppc-macos) + arch (x86, ppc-macos) ("stable")
Both the package version and the ebuild are widely tested, known to work and not have any serious issues on the indicated platform.
- ~arch (~x86, ~ppc-macos) + ~arch (~x86, ~ppc-macos) ("testing")
The package version and the ebuild are believed to work and do not have any @@ -53,7 +53,7 @@ The different levels of keyword are: is considered suitable for arch.
- No keyword + No keyword ("unkeyworded")
If a package has no keyword for a given arch, it means it is not known @@ -153,7 +153,7 @@ user system. -New packages should be marked as ~arch only upon +New packages should be marked as ~arch ("testing") only upon architectures for which the committing developer has tested. @@ -185,7 +185,7 @@ keyworded.

-Do not commit straight to arch. +Do not commit straight to arch ("stable").

@@ -196,10 +196,10 @@ Do not commit straight to arch.

-When upgrading, drop all existing keywords from arch to ~arch, and leave -any existing ~arch keywords intact. This must be done even if you think -you're just making a trivial fix there have been several examples of the -stable tree getting broken this way. +When upgrading, drop all existing keywords from arch to ~arch +("testing"), and leave any existing ~arch keywords intact. This must be +done even if you think you're just making a trivial fix there have +been several examples of the stable tree getting broken this way.

@@ -237,10 +237,11 @@ to do this.

-Stabilization, i.e., moving an ebuild from ~arch to arch, is done -by the relevant architecture teams. If you have access to exotic hardware but -are not on the arch teams, you may wish to make individual arrangements -the arch teams are happy for help, so long as they know what is going on. +Stabilization, i.e., moving an ebuild from ~arch ("testing") to +arch ("stable"), is done by the relevant architecture teams. If you have +access to exotic hardware but are not on the arch teams, you may wish to make +individual arrangements the arch teams are happy for help, so long as they +know what is going on.