Revision 14 as of 2004-08-08 01:59:49

Clear message

The release of Python 2.4 is scheduled for autumn 2004. An organized effort to go through the bug database and close irrelevant bugs or apply fixes would be very useful.

Location

Participants will convene 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

Transcripts of the #python-dev channel are being recorded at http://www.amk.ca/python/bugday/.

The list of bugs currently being worked on is recorded in the Wiki, on the PythonBugDayStatus page.

Procedures

The goal of the bug day is to process bug reports in [http://sourceforge.net/tracker/?group_id=5470&atid=105470 the Python bug tracker] on SourceForge, providing additional information so that the bug can be fixed and closed. Bugs should be processed in the fashion described by [http://www.python.org/peps/pep-0003.html PEP 3].

What to do:

Questions?

If you have questions about the bug day, please add them to this section.

Previous bug days

The first bug day was held Saturday, June 5, 2004, from 9AM to 6PM EDT, ending early because SourceForge CVS stopped working. 30 bugs were closed, and 14 more bugs had enough work done to make them closable.

The second bug day was held July 10 2004. 18 bugs and 21 patches were closed.

The third bug day was on Saturday, August 7th. 19 bugs and 12 patches were closed.

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.