For the impending 2.4alpha1 release, a coordinated effort to reduce the bug backlog would be good. Several other projects (Zope, GNOME, Mozilla) have "bug days" in which people meet on IRC and go through the bug database, closing irrelevant or incorrect reports, writing small test cases for vague reports, etc. Holding a Python bug day seems worth a try. I've written up a Wiki page, http://www.python.org/cgi-bin/moinmoin/PythonBugDay, to begin planning a bug day and to figure out what tools (if any) are required. Please comment, particularly if you've participated in bug days for Zope or other projects. Do we need transcripts of the IRC channel? Should we use #python or a new channel? If the details can get sorted out in time, perhaps we can have a bug day as soon as this weekend. Is a weekend day better than a weekday for people who are interested in participating? --amk
participants (9)
-
A.M. Kuchling
-
Brett C.
-
Chris McDonough
-
Gregory P. Smith
-
Jiwon Seo
-
Michael Hudson
-
Neil Schemenauer
-
Nick Bastin
-
Tim Peters