Revision 50 as of 2008-01-21 13:25:12

Clear message

Next Bug Day: Saturday, February 23, 2008

Time: all day. Participants are most likely to be around between 9AM to 3PM according to their local time.

Join us on IRC 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.

Preparatory Tasks

Location

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.

Links

Suggestions for bugs to tackle are recorded in this Wiki on the PythonBugDayStatus page.

PEP 0003, "Guidelines for Handling Bug Reports", describes the life cycle and how bugs should be processed by the developers.

Procedures

The goal of the bug day is to process bug reports in [http://bugs.python.org/ the Python bug tracker], trying to fix and close issues. Bugs should be processed in the fashion described by PEP 0003.

What to do:

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

Bug days for other projects

The [http://dev.zope.org/CVS/BugDays 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 [http://developer.gnome.org/projects/bugsquad/triage/faq.html their FAQ].

Unable to edit the page? See the FrontPage for instructions.