|
Size: 2265
Comment:
|
Size: 2496
Comment: Get page into final form
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| = Proposed schedule = | = Schedule = |
| Line 5: | Line 5: |
| The bug day will be on June XXX, 2004, from 9AM to 9PM EDT (1PM to 1AM GMT). | The bug day will be on Saturday, June 5, 2004, from 9AM to 9PM EDT (1PM to 1AM GMT). |
| Line 8: | Line 8: |
| (XXX should we use a different channel?) | To learn more about IRC and to find links to IRC clients for various platforms, see http://www.irchelp.org. |
| Line 12: | Line 12: |
| 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. | |
| Line 14: | Line 15: |
| Someone with write access to the bug database needs to be around at all times. Having people around with CVS write access would be nice so that fixes can get checked in,but is not necessary; the primary purpose is to improve bug reports, and if the fixes are applied later, that's fine. | What to do: |
| Line 16: | Line 17: |
| XXX How do people indicate which bugs they're working on? A wiki page? A channel message? The assigned-to field? - Maybe by setting the #channel title. (Not suitable, since there are multiple workers but only a single channel title) What to do: * If a problem isn't logged on SF, log it. * When you choose a bug to work on, announce it to the IRC channel. * If it's logged, consider providing a patch that fixes the problem, or at least a simple test case that demonstrates the bug. |
* If a problem isn't logged on SF, log it. See the [http://docs.python.org/lib/reporting-bugs.html 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.") * Consider providing a patch that fixes the problem, or at least a simple test case that demonstrates the bug. Does the bug appear to be gone in Python 2.3.4 or 2.4 CVS? Report that, too. |
| Line 28: | Line 28: |
| This is usually the most time-consuming step in the bug fixing process, so reading patches is very useful. |
|
| Line 29: | Line 31: |
| the fix to go into CVS. The SF bug tracker for Python has a _lot_ of bugs in it, and it's easy for bugs to be overlooked. |
the fix to go into CVS. The SF bug tracker for Python has a lot of bugs in it, and it's easy for bugs to be overlooked. * Feature requests can be added to the text of [http://www.python.org/peps/pep-0042.html PEP 42] and the bug closed. |
| Line 34: | Line 36: |
| * Write announcement and post it ASAP. * Set up [http://usefulinc.com/chump/ chump bot] |
|
| Line 38: | Line 38: |
| = Other processes = | = Questions? = If you have questions about the bug day, please add them to this section. = Other bug days = |
The release of Python 2.4alpha1 is currently scheduled for around July 1st. An organized effort to go through the bug database and close irrelevant bugs or apply fixes would be very useful.
Schedule
The bug day will be on Saturday, June 5, 2004, from 9AM to 9PM EDT (1PM to 1AM GMT).
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.
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:
- If a problem isn't logged on SF, log it. See the
[http://docs.python.org/lib/reporting-bugs.html 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.")
- Consider providing a patch that fixes the problem, or at least a simple test case that demonstrates the bug. Does the bug appear to be gone in Python 2.3.4 or 2.4 CVS? Report that, too.
- If someone else has supplied a fix, see if this fix works for you, and post 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 CVS. The SF bug tracker for Python has a lot of bugs in it, and it's easy for bugs to be overlooked.
Feature requests can be added to the text of [http://www.python.org/peps/pep-0042.html PEP 42] and the bug closed.
To Do
Set up [http://cvs.ilrt.org/cvsweb/redland/logger/ logger bot]
Questions?
If you have questions about the bug day, please add them to this section.
Other bug days
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].