Skip to content

Improve label versions triaging #1613

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

picnixz
Copy link
Member

@picnixz picnixz commented Jul 20, 2025

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/

@picnixz picnixz requested review from hugovk and AA-Turner July 20, 2025 10:27
Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants