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
devguide doesn't document all bug tracker components #59326
Comments
http://docs.python.org/devguide/triaging.html#components The undocumented components are:
|
I wonder why "None" exists, given that there's already "no selection" (maybe to distinguish issues that have been triaged already from the ones who haven't?). |
None has over 1300 issues, mostly old (historical). It could be removed from current use, I think (if it is possible to hide such a thing). Cross-build has just 6 issues collected together in last three months. I do not think that is really enough to justify adding it, but someone did. Mathias, can you define it? |
'None' is not available from the UI, and I suspect it's automatically set for issues reported via email. This might be a bug in Roundup, but I haven't verified it yet. |
Apparently it's set automatically on new issues if no other component is specified, even if the issue is created from the web interface. |
New changeset 2889f71c9e20 by Ezio Melotti in branch 'default': |
I documented the email component, and removed the "None" component. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: