diff --git a/pep-0003.txt b/pep-0003.txt index f2c8a12d1..9808c753e 100644 --- a/pep-0003.txt +++ b/pep-0003.txt @@ -14,6 +14,13 @@ Introduction a list of people willing to handle bug reports and their areas of expertise. + These are guidlines for the developers of Python, not the + submitters of bugs. Those are at + + http://docs.python.org/lib/reporting-bugs.html + + (though this hardly seems the best place). + Guidelines @@ -27,16 +34,18 @@ Guidelines request", "later", and "closed"; and add a comment to the bug saying that this is the case (mentioning the PEP explicitly). + XXX do we prefer the feature request tracker or PEP 42? + 3. Assign the bug a reasonable priority. We don't yet have a clear sense of what each priority should mean, except than 9 is highest and 1 is lowest. One rule, however, is that bugs with priority seven or higher must be fixed before the next release. 4. If a bug report doesn't have enough information to allow you to - reproduce or diagnose it, send email to the original submittor - and ask for more information. If the original report is really - thin and your email doesn't get a response after a reasonable - waiting period, you can close the bug. + reproduce or diagnose it, ask the original submitter for more + information. If the original report is really thin and your + email doesn't get a response after a reasonable waiting period, + you can close the bug. 5. If you fix a bug, mark the status as "Fixed" and close it. In the comments, include the CVS revision numbers of the @@ -44,10 +53,9 @@ Guidelines SourceForge bug number *and* a normal description of the change. - 6. If you are assigned a bug that you are unable to deal with - assign it to someone else. The guys at PythonLabs get paid to - fix these bugs, so pick one of them if there is no other - obvious candidate. + 6. If you are assigned a bug that you are unable to deal with, + assign it to someone else if you think they will be able to + deal with it, otherwise it's probably best to unassign it. References