iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Minimal update w.r.t. new bug tracker.

This commit is contained in:
Georg Brandl 2007-12-08 10:48:07 +00:00
parent c44ee8f1ad
commit 443ca7a7fb
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
pep-0003.txt
View File

@ -11,7 +11,7 @@ Post-History:
Introduction Introduction
This PEP contains guidelines for handling bug reports to the This PEP contains guidelines for handling bug reports to the
Python project on SourceForge[1]. Still to be done is to collect Python project at the tracker [1]. Still to be done is to collect
a list of people willing to handle bug reports and their areas of a list of people willing to handle bug reports and their areas of
expertise. expertise.
@ -35,12 +35,12 @@ Guidelines
request", "later", and "closed"; and add a comment to the bug request", "later", and "closed"; and add a comment to the bug
saying that this is the case (mentioning the PEP explicitly). saying that this is the case (mentioning the PEP explicitly).
XXX do we prefer the feature request tracker or PEP 42? XXX do we prefer the tracker or PEP 42?
3. Assign the bug a reasonable priority. We don't yet have a 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 clear sense of what each priority should mean. One rule,
highest and 1 is lowest. One rule, however, is that bugs with however, is that bugs with priority "urgent" or higher must
priority seven or higher must be fixed before the next release. be fixed before the next release.
4. If a bug report doesn't have enough information to allow you to 4. If a bug report doesn't have enough information to allow you to
reproduce or diagnose it, ask the original submitter for more reproduce or diagnose it, ask the original submitter for more
@ -49,10 +49,10 @@ Guidelines
you can close the bug. you can close the bug.
5. If you fix a bug, mark the status as "Fixed" and close it. In 5. If you fix a bug, mark the status as "Fixed" and close it. In
the comments, include the CVS revision numbers of the the comments, include the SVN revision numbers of the commit(s).
affected files. In the CVS checkin message, include the In the SVN checkin message, include the issue number *and* a
SourceForge bug number *and* a normal description of the normal description of the change, mentioning the contributor
change. if a patch was applied.
6. If you are assigned a bug that you are unable to deal with, 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 assign it to someone else if you think they will be able to
@ -61,4 +61,4 @@ Guidelines
References References
[1] http://sourceforge.net/projects/python [1] http://bugs.python.org/