|
Size: 7039
Comment:
|
Size: 7184
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 50: | Line 50: |
| There are various things MissingFromDocumentation; these tasks mostly require writing and editing, not programming. | ##RDM20101116 The below page is currently empty ##There are various things MissingFromDocumentation; these tasks mostly require writing and editing, not programming. |
| Line 58: | Line 59: |
| Bugs should be processed in the fashion described by PEP PEP:0003, "Guidelines for Handling Bug Reports". | ## RDM20101116 PEP 0003 is too out of date to be useful. ## Bugs should be processed in the fashion described by PEP PEP:0003, "Guidelines for Handling Bug Reports". |
| Line 86: | Line 88: |
| * [add notes here as needed] |
Next Python Bug Day: November 20th and 21st
Time: all weekend
Join us for an effort at closing some Python bugs and patches. Get quick feedback on your patches and bugfixes, or learn how to submit and examine patches.
Participating Online
Participants will meet in the #python-dev IRC channel on irc.freenode.net. To learn more about IRC and to find links to IRC clients for various platforms, see http://www.irchelp.org.
Finding Bugs
Using the bug tracker, you can perform various searches to look for candidate issues:
Procedures
The goal of the bug day is to process bug reports in the Python bug tracker, trying to fix and close issues.
At PyCon 2008, Brett Cannon provided a slideshow educating new contributors to the Python code.
What to do:
Grab a copy of the Python SVN trunk. See the development FAQ for instructions. If anonymous access isn't working, you can download a snapshot from the daily snapshot directory.
See also Getting Set Up and Issue Workflow.
If you have a problem that isn't in the bug tracker, announce it to the IRC channel, and if it's more than five minutes' work, create a bug report for it. See the bug reporting instructions to learn how to write bug reports.
- When you choose a bug to work on, announce it to the IRC channel. (e.g. "I'm working on #123456.") This avoids accidentally duplicating work.
Consider providing a patch that fixes the problem, or at least a simple test case that demonstrates the bug. Please see the patch submission guidelines before submitting a patch.
- Does the bug appear to be gone in the Python 3.x trunk, but not the 3.1 or 2.7 maintenance branchs? Report that, too.
- If someone else has supplied a fix, see if this fix works for you, and add your results to the bug.
- Read the text of proposed patches and assess them for correctness and code quality. This is usually the most time-consuming step in the bug fixing process, so reading patches is very useful.
- If there's a working fix, feel free to add a note asking for the fix to go into SVN. The bug tracker has a lot of items in it, and it's easy for bugs to be overlooked.
- Feature requests should be classified as type 'feature request' in the bug tracker.
For later committing
- [add notes here as needed]
Questions?
If you have questions about the bug day, please add them to this section.
Previous bug days
Date |
Accomplishments |
2004-06-05 |
44 bugs |
2004-07-10 |
18 bugs, 21 patches |
2004-08-07 |
19 bugs, 12 patches |
2004-11-07 |
12 bugs, 10 patches |
2005-06-25 |
10 bugs, 7 patches |
2005-12-04 |
11 bugs+patches |
2006-03-31 |
19 bugs, 9 patches |
2008-01-19 |
37 bugs+patches |
2008-02-23 |
48 bugs+patches |
2008-05-10 & 11 |
34 bugs+patches |
2009-04-25 |
Bug days for other projects
The Zope bug day has a good description of what to do, though the details of the bug tracker are specific to the Zope project.
The GNOME community holds regular Bug Days; the procedures are described in their FAQ.
Preparatory Tasks
- Need to set up log of python-dev channel
- Send announcements (python-announce, python-dev, PSF weblog, personal web log. python-list?)