@@ -98,7 +98,8 @@ These labels are used to indicate which versions of Python are affected.
9898The available version labels (with the form :samp: `3.{ N } `) are updated
9999whenever new feature releases are created or retired.
100100
101- Triagers may adhere to the following recommendations:
101+ Recommendations
102+ ---------------
102103
103104- For security issues, add the :gh-label: `type-security ` label and
104105 the affected version labels. This makes the issue stand out.
@@ -107,14 +108,10 @@ Triagers may adhere to the following recommendations:
107108 the :gh-label: `type-bug ` label as knowing which versions are affected
108109 does not give more information.
109110
110- Once the bug is resolved, one can optionally add the version labels for
111- the affected versions. This helps readers in knowing whether their issue
112- has been solved for their Python version.
111+ - Labels for end-of-life versions should be removed when possible but there is
112+ no need to explicitly go through old issues to remove such labels.
113113
114- - EOL version labels should be removed when possible but there is no need
115- to explicitly go through old issues to remove such labels.
116-
117- - Otherwise, add the corresponding version label(s) and remember to
114+ - Otherwise, add the corresponding version labels and remember to
118115 update them when the latest major version is updated.
119116
120117See also :ref: `the branch status page <branchstatus >`
@@ -135,7 +132,7 @@ cases subject to the release manager approval:
135132 version under development would now be :samp: `3.{ N+1 } .0a1 `.
136133
137134 To indicate that the labelling is correct and the extension is
138- approved, the :gh-label: `triaged ` label could also be applied.
135+ approved, the :gh-label: `triaged ` label can also be applied.
139136
140137
141138.. _Keywords :
0 commit comments