-
-
Notifications
You must be signed in to change notification settings - Fork 60
Add label: OS-unsupported #526
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
Comments
I think this is a very good idea. |
There are at least 3 ways this can be automated:
The last option would be ideal because it requires no human intervention, but it would rely on queries like
Note that nowadays triagers are able to add issues to project, and can do so from the right sidebar of the issue, just like they add labels. The downside is that they have to remember that projects exists and have to edit two separate fields (labels and projects) instead of just one (labels). |
That's the main reason I'm proposing a label. All triagers know how to apply labels, so this doesn't change/complicate the process for them. Another reason is that labels are visible in overviews. |
Devguide PR: python/devguide#1281 |
Uh oh!
There was an error while loading. Please reload this page.
Request for label changes on
python/cpython
I'm proposing a
OS-unsupported
label, to be used for platforms not listed in PEP-11.If I understand correctly, we can set things up such that labeled issues are automatically added to a dedicated project, where they can be categorized/handled later. This way, devs/triagers wouldn't need to care about GitHub projects, or “community-supported” platforms. Unless they want to :)
Broader discussion: https://discuss.python.org/t/44621/2
The text was updated successfully, but these errors were encountered: