This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Document the "type" field of the tracker in the devguide
Type: Stage: resolved
Components: Devguide Versions:
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: ezio.melotti Nosy List: eric.araujo, ezio.melotti, georg.brandl, terry.reedy
Priority: normal Keywords: patch

Created on 2011-08-20 09:50 by ezio.melotti, last changed 2022-04-11 14:57 by admin. This issue is now closed.

File name Uploaded Description Edit
issue12792.diff ezio.melotti, 2011-08-20 09:50
Messages (7)
msg142520 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2011-08-20 09:50
The attached patch adds documentation for the "type" field of the tracker to the devguide/triaging page.
This is also related to the meta issue #393 [0].

msg142544 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2011-08-20 17:53
This documents the current list, but ;-) I think the current list should be modified.

1. Put behavior at the top of the list, as it is the most common (a 'human factor' principle).

2. Combine performance and resource usage. Both are extremely rare and largely overlap. Time is a resource and space-hogging is bad performance. There is no difference as far as I know in terms of how we treat issues.

3. Going further: Each category should have a reason for being in terms of how we treat issues. I really think behavior, feature request, security, and other (listed in that order) are sufficient. Compiler errors, for instance, are rare (2% overall and probably less now), are covered by the build component, and are treated like bugs anyway (fixes are applied to current versions.
msg142563 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2011-08-20 21:13
I believe you can’t capitalize “behavior” in English.

About Terry’s 3): I think the usefulness of having separate types is the same as components, to let people search for what they can help with.
msg142594 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2011-08-21 06:51
You mean "pluralize" I guess.
msg142597 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2011-08-21 08:15
I did!
msg142638 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2011-08-21 18:56
'Behaviors' is quite legal. However,
    Wrong or unexpected behaviors/results/exceptions. ..."
could well be
    Wrong or unexpected behavior, result, or exception. ..."
msg142758 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2011-08-22 21:57
Fixed in aa627513fb23.  I also moved the 'behavior' at the beginning of the list.
Date User Action Args
2022-04-11 14:57:20adminsetgithub: 57001
2011-08-22 21:57:08ezio.melottisetstatus: open -> closed
resolution: fixed
messages: + msg142758

stage: patch review -> resolved
2011-08-21 18:56:23terry.reedysetmessages: + msg142638
2011-08-21 08:15:24eric.araujosetmessages: + msg142597
2011-08-21 06:51:37georg.brandlsetnosy: + georg.brandl
messages: + msg142594
2011-08-20 21:13:10eric.araujosetmessages: + msg142563
2011-08-20 17:53:57terry.reedysetmessages: + msg142544
2011-08-20 09:50:36ezio.melotticreate