[A.M. Kuchling] > 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. A bug day is an excellent idea. In the Zope world, it's the only way any bugs get fixed <wink>. > Do we need transcripts of the IRC channel? When a bug gets closed or rejected, and the OP protests, it can be useful to paste snippets of the IRC session wherein the issue was discussed. Most people save their own transcripts for this purpose. Don't see a need for "an official" transcript. > Should we use #python or a new channel? No opinion. > 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? A weekday would be impossible for at least me and Fred.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4