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 C9E3B138350 for ; Fri, 10 Apr 2020 07:01:45 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 392EBE0968; Fri, 10 Apr 2020 06:59:24 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (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 DEB69E0963 for ; Fri, 10 Apr 2020 06:59:23 +0000 (UTC) Received: from localhost.localdomain (c143-158.icpnet.pl [85.221.143.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 7F03034EFFE; Fri, 10 Apr 2020 06:59:22 +0000 (UTC) From: =?UTF-8?q?Micha=C5=82=20G=C3=B3rny?= To: gentoo-dev@lists.gentoo.org Cc: =?UTF-8?q?Micha=C5=82=20G=C3=B3rny?= Subject: [gentoo-dev] [PATCH 07/10] glep-0072: Combine and amend description of states Date: Fri, 10 Apr 2020 08:58:44 +0200 Message-Id: <20200410065847.96199-8-mgorny@gentoo.org> X-Mailer: git-send-email 2.26.0 In-Reply-To: <20200410065847.96199-1-mgorny@gentoo.org> References: <20200410065847.96199-1-mgorny@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: ac71ef18-a1f6-4d07-b1e9-a01ab79317fb X-Archives-Hash: 86f7f2ea83f1ab42f71b8ce82ee57f39 Provide a combined description for every status that explains what it means, how it's used by linting tools and how it affects stabilization requests. Signed-off-by: Michał Górny --- glep-0072.rst | 46 +++++++++++++++++++--------------------------- 1 file changed, 19 insertions(+), 27 deletions(-) diff --git a/glep-0072.rst b/glep-0072.rst index d6e96d5..fe3e0e5 100644 --- a/glep-0072.rst +++ b/glep-0072.rst @@ -111,49 +111,41 @@ On introduction, the setting will be ``stable`` for all architectures using stable keywords, and ``testing`` for those that do not (``alpha``, ``mips``, ``riscv``, Prefix profiles at the moment). -Meaning of the values for repoman ---------------------------------- +Meaning of the values +--------------------- stable ~~~~~~ -When a profile of an architecture arch is tested, then repoman checks -consistency of the dependency tree for ``arch`` and for ``~arch`` separately. +Stable means that the architecture is actively maintaning stable keywords. +When dependency graphs of packages with stable keywords are tested, they +are tested separately for ``arch`` and ``~arch`` systems. -Which profiles of the architecture are tested is still controlled -by profiles.desc (and ``-d`` / ``-e`` switches). +Stable architectures are listed first in keyword-relevant contexts (``eshowkw``, +Bugzilla) and developers are expected to file stabilization requests on these +arches. This is the current behaviour and shall be the default if nothing is specified for an architecture. degraded ~~~~~~~~ -When a profile of an architecture is tested, then repoman treats ``arch`` -in ebuilds as ``~arch``, and tests consistency only for ``~arch``. +Degraded means that the architecture does not maintain a consistent stable +dependency graph but uses stable keywords on some packages. When dependency +graphs of packages with stable keywords are tested, they are tested only +for ``~arch`` systems, i.e. stable keywords are ignored. -Which profiles of the arch are tested is still controlled by profiles.desc -(and ``-d`` / ``-e`` switches). +Degraded architectures are generally listed after stable architectures, +possibly mixed with testing. Developers are not expected to file stabilization +requests. -A new switch for repoman may be provided to temporarily upgrade +A new switch for linting tools may be provided to temporarily upgrade an architecture from ``degraded`` to ``stable`` status (for architecture team work). testing ~~~~~~~ -When a profile of an architecture is tested, then repoman treats ``arch`` -as an error and aborts. Consistency is only tested for ``~arch``. - -Which profiles of the arch are tested is still controlled by profiles.desc -(and ``-d`` / ``-e`` switches). - -Meaning of the values for other tools -------------------------------------- - -All architectures with the value ``stable`` are considered as stable -architectures, in the sense that - -- they require stabilization requests on bugzilla, which are handled - by an arch team -- they may, e.g., be listed first by tools such as eshowkw -- and similar, to the discretion of tool authors +Testing means that the architecture does not use stable keywords at all. +Presence of such keywords is considered an error. Consistency is tested +only for ``~arch``. Backwards Compatibility -- 2.26.0