Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
picnixz wants to merge4 commits intopython:main
base:main
Choose a base branch
Loading
frompicnixz:feat/workflow/triage-version-labels
Open
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 35 additions & 1 deletiontriage/labels.rst
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -27,7 +27,8 @@ These labels are used to specify the type of issue:
core dump.
* :gh-label:`type-feature`: for feature requests or enhancements.
Feature requests do not need :ref:`version labels <Version labels>`;
it is implicit that features are added to the ``main`` branch only.
it is implicit that features are added to the ``main`` branch only,
except for some :ref:`exceptional cases <exceptional-version-labels>`.
The `Ideas Discourse category`_ can be used to discuss enhancements
before filing an issue.
* :gh-label:`type-security`: for security issues.
Expand DownExpand Up@@ -97,9 +98,42 @@ These labels are used to indicate which versions of Python are affected.
The available version labels (with the form :samp:`3.{N}`) are updated
whenever new feature releases are created or retired.

Recommendations
Copy link
Member

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?)?

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?

devdanzin reacted with thumbs up emoji
---------------

- For security issues, add the :gh-label:`type-security` label and
the affected version labels. This makes the issue stand out.

- For non-security issues affecting *all* bugfix branches, only add
the :gh-label:`type-bug` label as knowing which versions are affected
does not give more information.

- Labels for end-of-life versions should be removed when possible but there is
no need to explicitly go through old issues to remove such labels.

- Otherwise, add the corresponding version labels and remember to
update them when the latest feature version is released.

See also :ref:`the branch status page <branchstatus>`
for a list of active branches.

.. _exceptional-version-labels:

Exceptional version labels for features
---------------------------------------

While features should not have a version label, there are a few exceptional
cases subject to the release manager approval:

- 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.
Comment on lines +128 to +135
Copy link
MemberAuthor

@picnixzpicnixzDec 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

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

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.



.. _Keywords:
.. _Other:
Expand Down
Loading
[8]ページ先頭
©2009-2025 Movatter.jp