[issue15121] devguide doesn't document all bug tracker components

Ezio Melotti added the comment: I documented the email component, and removed the "None" component. I'm still not sure what to do about Cross-build -- maybe it should be removed as well. Its name is self-explanatory, so even if it's not removed and it's not documented I don't think it's a big

[issue15121] devguide doesn't document all bug tracker components

Roundup Robot added the comment: New changeset 2889f71c9e20 by Ezio Melotti in branch 'default': #15121: document the "email" component. http://hg.python.org/devguide/rev/2889f71c9e20 -- nosy: +python-dev ___ Python tracker

[issue15121] devguide doesn't document all bug tracker components

Ezio Melotti added the comment: > I suspect it's automatically set for issues reported via email Apparently it's set automatically on new issues if no other component is specified, even if the issue is created from the web interface. -- ___ Python t

[issue15121] devguide doesn't document all bug tracker components

Ezio Melotti added the comment: '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. -- ___ Python tracker

[issue15121] devguide doesn't document all bug tracker components

Terry J. Reedy added the comment: 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

[issue15121] devguide doesn't document all bug tracker components

Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue15121] devguide doesn't document all bug tracker components

Ezio Melotti added the comment: 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?). "email" refers to issue related to the email package, and I'm not sure what exactly classify as cross-b

[issue15121] devguide doesn't document all bug tracker components

New submission from Petri Lehtinen : http://docs.python.org/devguide/triaging.html#components The undocumented components are: - None - Cross-Build - email -- components: Devguide messages: 163321 nosy: ezio.melotti, petri.lehtinen priority: normal severity: normal status: open title: d