Improve label versions triaging #1613
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com>
hugovk
reviewed
Aug 7, 2025
triage/labels.rst
Outdated
Comment on lines
131
to
138
| - If we are currently in the *beta* period of :samp:`3.{N}.0` and | ||
| if a feature was implemented in its *alpha* period but requires a | ||
| non-trivial extension (hence a new *feature* issue), this new | ||
| feature issue is given the :samp:`3.{N}` label as the latest | ||
| version under development would now be :samp:`3.{N+1}.0a1`. | ||
|
|
||
| To indicate that the labelling is correct and the extension is | ||
| approved, the :gh-label:`triaged` label could also be applied. |
There was a problem hiding this comment.
Hmm, not sure if we need this? And I'm not sure about the triage label suggestion, it doesn't really say anything more than "issue is accepted by a triager".
There was a problem hiding this comment.
Actually, it's for a visual tag. Sometimes I don't remember the issues I've triaged. And if I see an issue with weird label I would say "oh this one could have been mistriaged maybe". But with a triaged label, I know that I don't need to change the labels (same for when I lack a topic-* or a directory for an issue; when there is just "type-bug" it's kind of .. hard to know that there is actually a project associated to the issue; projects can't be seen on the issue page)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some people asked me about how I actually apply my labels while triaging and I think I could actually share my workflow in the devguide instead for future triaging. I especially think that it's not necessary for bugs that span across all active versions to be labelled with the all labels... Ideally, I would have wanted a 3.X+ tag which implies that the bug started appearing in 3.X, and a bot would be able to automate the labels every time a new one is added but this would be a separate issue.
cc @hugovk
📚 Documentation preview 📚: https://cpython-devguide--1613.org.readthedocs.build/