1 |
Provide a combined description for every status that explains what it |
2 |
means, how it's used by linting tools and how it affects stabilization |
3 |
requests. |
4 |
|
5 |
Signed-off-by: Michał Górny <mgorny@g.o> |
6 |
--- |
7 |
glep-0072.rst | 46 +++++++++++++++++++--------------------------- |
8 |
1 file changed, 19 insertions(+), 27 deletions(-) |
9 |
|
10 |
diff --git a/glep-0072.rst b/glep-0072.rst |
11 |
index 33a9578..d3afaef 100644 |
12 |
--- a/glep-0072.rst |
13 |
+++ b/glep-0072.rst |
14 |
@@ -112,49 +112,41 @@ On introduction, the setting will be ``stable`` for all architectures using |
15 |
stable keywords, and ``testing`` for those that do not (``alpha``, ``mips``, |
16 |
``riscv``, Prefix profiles at the moment). |
17 |
|
18 |
-Meaning of the values for repoman |
19 |
---------------------------------- |
20 |
+Meaning of the values |
21 |
+--------------------- |
22 |
stable |
23 |
~~~~~~ |
24 |
-When a profile of an architecture arch is tested, then repoman checks |
25 |
-consistency of the dependency tree for ``arch`` and for ``~arch`` separately. |
26 |
+Stable means that the architecture is actively maintaning stable keywords. |
27 |
+When dependency graphs of packages with stable keywords are tested, they |
28 |
+are tested separately for ``arch`` and ``~arch`` systems. |
29 |
|
30 |
-Which profiles of the architecture are tested is still controlled |
31 |
-by profiles.desc (and ``-d`` / ``-e`` switches). |
32 |
+Stable architectures are listed first in keyword-relevant contexts (``eshowkw``, |
33 |
+Bugzilla) and developers are expected to file stabilization requests on these |
34 |
+arches. |
35 |
|
36 |
This is the current behaviour and shall be the default if nothing is specified |
37 |
for an architecture. |
38 |
|
39 |
transitional |
40 |
~~~~~~~~~~~~ |
41 |
-When a profile of an architecture is tested, then repoman treats ``arch`` |
42 |
-in ebuilds as ``~arch``, and tests consistency only for ``~arch``. |
43 |
+Transitional means that the architecture does not maintain a consistent stable |
44 |
+dependency graph but uses stable keywords on some packages. When dependency |
45 |
+graphs of packages with stable keywords are tested, they are tested only |
46 |
+for ``~arch`` systems, i.e. stable keywords are ignored. |
47 |
|
48 |
-Which profiles of the arch are tested is still controlled by profiles.desc |
49 |
-(and ``-d`` / ``-e`` switches). |
50 |
+Transitional architectures are generally listed after stable architectures, |
51 |
+possibly mixed with testing. Developers are not expected to file stabilization |
52 |
+requests. |
53 |
|
54 |
-A new switch for repoman may be provided to temporarily upgrade |
55 |
+A new switch for linting tools may be provided to temporarily upgrade |
56 |
an architecture from ``transitional`` to ``stable`` status (for architecture |
57 |
team work). |
58 |
|
59 |
testing |
60 |
~~~~~~~ |
61 |
-When a profile of an architecture is tested, then repoman treats ``arch`` |
62 |
-as an error and aborts. Consistency is only tested for ``~arch``. |
63 |
- |
64 |
-Which profiles of the arch are tested is still controlled by profiles.desc |
65 |
-(and ``-d`` / ``-e`` switches). |
66 |
- |
67 |
-Meaning of the values for other tools |
68 |
-------------------------------------- |
69 |
- |
70 |
-All architectures with the value ``stable`` are considered as stable |
71 |
-architectures, in the sense that |
72 |
- |
73 |
-- they require stabilization requests on bugzilla, which are handled |
74 |
- by an arch team |
75 |
-- they may, e.g., be listed first by tools such as eshowkw |
76 |
-- and similar, to the discretion of tool authors |
77 |
+Testing means that the architecture does not use stable keywords at all. |
78 |
+Presence of such keywords is considered an error. Consistency is tested |
79 |
+only for ``~arch``. |
80 |
|
81 |
|
82 |
Backwards Compatibility |
83 |
-- |
84 |
2.26.0 |