@@ -54,29 +54,31 @@ These labels are mostly used to specify which :ref:`part of the codebase
54
54
(written in Python) and other changes related to tests, :mod: `unittest `,
55
55
or :mod: `doctest `.
56
56
57
+ OS labels
58
+ =========
57
59
58
- Expert labels
59
- =============
60
+ These labels are used to specify which operating systems are affected.
61
+ Since most issues either affect all systems or are specific to Unix,
62
+ the only available labels are :gh-label: `OS-windows `, :gh-label: `OS-mac `,
63
+ and :gh-label: `OS-freebsd `.
64
+
65
+
66
+ .. _Expert labels :
67
+ .. _Topic labels :
68
+
69
+ Topic labels
70
+ ============
60
71
61
- These labels are used to specify the area of expertise required to address
72
+ These labels are used to denote the specific topic area, if any, of
62
73
the issue/PR. This includes both specific modules/packages and generic
63
74
interest areas.
64
75
65
76
Adding these labels is also a way to notify the relevant experts, since
66
77
they are encouraged to subscribe to them. Depending on the label,
67
78
this might also automatically add the issue to a GitHub project.
68
79
69
- You can see the `full list of expert labels on GitHub
70
- <https://github.com/python/cpython/labels?q=expert> `_.
71
-
72
-
73
- OS labels
74
- =========
75
-
76
- These labels are used to specify which operating systems are affected.
77
- Since most issues either affect all systems or are specific to Unix,
78
- the only available labels are :gh-label: `OS-windows `, :gh-label: `OS-mac `,
79
- and :gh-label: `OS-freebsd `.
80
+ You can see the `full list of topic labels on GitHub
81
+ <https://github.com/python/cpython/labels?q=topic> `_.
80
82
81
83
82
84
Version labels
0 commit comments