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/

improve label versions triaging

10c2b84

picnixz requested review fromAA-Turner andhugovk

July 20, 2025 10:27

StanFromIreland reviewed

Jul 20, 2025

View reviewed changes

triage/labels.rst OutdatedShow resolvedHide resolved

Update triage/labels.rst

03c1d37

Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com>

StanFromIreland reviewed

Aug 6, 2025

View reviewed changes

triage/labels.rst OutdatedShow resolvedHide resolved

StanFromIreland requested a review fromezio-melotti

August 6, 2025 19:42

hugovk reviewed

Aug 7, 2025

View reviewed changes

triage/labels.rst OutdatedShow resolvedHide resolved

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.

Copy link

Member

hugovkAug 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

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".

Copy link

MemberAuthor

picnixzAug 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

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)

address reviews

d8c7a7b

devdanzin reviewed

Sep 17, 2025

View reviewed changes

triage/labels.rst

		The available version labels (with the form:samp:`3.{N}`) are updated
		whenever new feature releases are created or retired.

		Recommendations

Copy link

Member

devdanzinSep 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Maybe add a recommendation about whether to keeptype-bug intype-security issues (are they truly redundant?)?

Copy link

Member

StanFromIrelandSep 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I think that the place for that is beside the type-security doc?

StanFromIreland mentioned this pull request

Oct 28, 2025

Feature: Clarify that docs issues typically don't get version labels#1674

Open

StanFromIreland approved these changes

Dec 5, 2025

View reviewed changes

Copy link

Member

StanFromIreland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

LGTM

hugovk reviewed

Dec 6, 2025

View reviewed changes

triage/labels.rst OutdatedShow resolvedHide resolved

triage/labels.rstShow resolvedHide resolved

Update triage/labels.rst

746e517

Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>

picnixz commented

Dec 7, 2025

View reviewed changes

triage/labels.rst

Comment on lines +128 to +135

		- 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 can also be applied.

Copy link

MemberAuthor

picnixzDec 7, 2025•
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Suggested change

	-Ifwe 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 can also be applied.
	-Assume thatwe are currently in the beta period of:samp:`3.{N}.0`,
	that is, the latest version under development is:samp:`3.{N+1}.0a1`.
	If a feature implemented in the alpha period of:samp:`3.{N}.0`
	requires a non-trivial extension, a new feature issue must be
	created and be given the:samp:`3.{N}` label.

	To indicate that the labelling is correct and the extension is
	approved, the:gh-label:`triaged` label can also be applied.

Copy link

MemberAuthor

picnixzDec 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

@hugovk Something like this?

Copy link

MemberAuthor

picnixzDec 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Note: another acceptable3.N label is when we implement a PEP. It's good to have both feature & 3.N labels at the same time because the PEP is meant to be implemented in that version.

Labels

None yet

Movatterモバイル変換

Uh oh!

Improve label versions triaging#1613

Are you sure you want to change the base?

Improve label versions triaging#1613

Uh oh!

Conversation

picnixz commentedJul 20, 2025• edited by github-actionsbotLoading Uh oh!There was an error while loading.Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

hugovkAug 7, 2025

Choose a reason for hiding this comment

Uh oh!

picnixzAug 7, 2025

Choose a reason for hiding this comment

Uh oh!

devdanzinSep 17, 2025

Choose a reason for hiding this comment

Uh oh!

StanFromIrelandSep 17, 2025

Choose a reason for hiding this comment

Uh oh!

StanFromIreland left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

picnixzDec 7, 2025• editedLoading Uh oh!There was an error while loading.Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

picnixzDec 7, 2025

Choose a reason for hiding this comment

Uh oh!

picnixzDec 7, 2025

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

picnixz commentedJul 20, 2025•
edited by github-actionsbot
Loading

picnixzDec 7, 2025•
edited
Loading