|
Size: 2135
Comment: Use #python-dev; fix typo
|
← Revision 96 as of 2013-09-03 17:38:06 ⇥
Size: 5435
Comment: spam
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| 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. | |
| Line 3: | Line 2: |
| = Proposed schedule = | '''(!) Next Python Bug Day: November 3rd''' |
| Line 5: | Line 4: |
| The bug day will be on June XXX, 2004, from 9AM to 9PM EDT (1PM to 1AM GMT). | |
| Line 7: | Line 5: |
| Participants will convene in the #python-dev IRC channel on irc.freenode.net. (XXX should we use a different channel?) |
Time: all Saturday Join us 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. To get all set up, the [[http://docs.python.org/devguide|Developer's Guide]] contains all the information you need. There are usually a few core developers around at any time. Here are the nicknames of developers who will be present for sure: * merwok — Éric Araujo — American East Coast timezone * = Participating at Your User Group = The Montréal-Python user group will meet up in person to participate in the bug day. Some Python user groups will meet up in person during the weekend. Is your local user group participating? = Participating Online = 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/|http://www.irchelp.org]]. = Finding Bugs = Using [[http://bugs.python.org/|the bug tracker]], you can perform various searches to look for candidate issues: * [[http://bugs.python.org/issue?@search_text=&title=&@columns=title&id=&@columns=id&creation=&creator=&activity=&@columns=activity&@sort=activity&actor=&nosy=&type=&components=&versions=&severity=&dependencies=&assignee=&keywords=6&priority=&@group=priority&status=1&@columns=status&resolution=&@pagesize=50&@startwith=0&@queryname=&@old-queryname=&@action=search|Bugs classified as 'easy']] * [[http://bugs.python.org/issue?@search_text=&title=&@columns=title&id=&@columns=id&creation=&creator=&activity=&@columns=activity&@sort=activity&actor=&nosy=&type=&components=4&versions=&severity=&dependencies=&assignee=&keywords=&priority=&@group=priority&status=1&@columns=status&resolution=&@pagesize=50&@startwith=0&@queryname=&@old-queryname=&@action=search|Documentation bugs]] * [[http://bugs.python.org/issue?@action=random|Random issue]] (you can use the link in the left sidebar of the bug tracker to go through random issues until you find one that you like |
| Line 12: | Line 61: |
| Bugs should be processed in the fashion described by [http://www.python.org/peps/pep-0003.html PEP 3]. | |
| Line 14: | Line 62: |
| 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. | 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. |
| Line 16: | Line 64: |
| 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) |
|
| Line 20: | Line 65: |
| XXX do we need to set up a web transcript of the channel? Perhaps a [http://usefulinc.com/chump/ chump bot?] | |
| Line 23: | Line 81: |
| * If a problem isn't logged on SF, log it. * If it's logged, consider providing a patch that fixes the problem, or at least a simple test case that demonstrates the bug. * 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. * 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. |
|
| Line 34: | Line 83: |
| = Other processes = 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 specified 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]. |
* Grab a copy of the Python codebase from Mercurial, following instructions in the [[http://docs.python.org/devguide|Developer's Guide]], and compile it. * If you have a problem that isn't in the bug tracker, announce it to the IRC channel, and if it's more than five minutes' work, create a bug report for it. See the [[http://docs.python.org/dev/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.") or on the bug report itself. This avoids accidentally duplicating work. * Consider providing a patch that fixes the problem, or at least a simple test case that demonstrates the bug. Please see the patch submission guidelines in the Developer's Guide before submitting a patch. * Does the bug appear to be gone in the Python development version (the Mercurial branch "default", that will become 3.4), but not the 3.2, 3.3 or 2.7 maintenance branchs? Report that, too. * If someone else has supplied a fix, see if this fix works for² you, and add 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 get committed. The bug tracker has a lot of items in it, and it's easy for bugs to be overlooked. * Feature requests should be classified as type 'feature request' in the bug tracker. |
| Line 41: | Line 94: |
| = 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 || ||2008-02-23 ||48 bugs+patches || ||2008-05-10 & 11 ||34 bugs+patches || ||2009-04-25 ||[[http://bugs.python.org/issue?@columns=title&@columns=id&activity=from+2009-04-25+to+2009-04-%20%2026&@columns=activity&@sort=activity&@group=priority&status=2&@columns=status&@pagesize=50&@startwith=0&@action=search|39 bugs]] || ||2010-11-20 & 21 ||[[http://bugs.python.org/issue?@columns=title&@columns=id&activity=from+2010-11-20+to+2010-11-22&@columns=activity&@sort=activity&@group=priority&status=2&@columns=status&@pagesize=100&@startwith=0&@action=search|55 bugs]] || ||2012-11-03 ||[[http://bugs.python.org/issue?@columns=title&@columns=id&activity=from+2012-11-03+to+2012-11-04&@columns=activity&@sort=activity&@group=priority&status=2&@columns=status&@pagesize=100&@startwith=0&@action=search|17 bugs]] || = Preparatory Tasks = * Need to set up log of python-dev channel * Send announcements (python-announce, python-dev, PSF weblog, personal web log. python-list?) |
(!) Next Python Bug Day: November 3rd
Time: all Saturday
Join us 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.
To get all set up, the Developer's Guide contains all the information you need.
There are usually a few core developers around at any time. Here are the nicknames of developers who will be present for sure:
- merwok — Éric Araujo — American East Coast timezone
Participating at Your User Group
The Montréal-Python user group will meet up in person to participate in the bug day. Some Python user groups will meet up in person during the weekend.
Is your local user group participating?
Participating Online
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.
Finding Bugs
Using the bug tracker, you can perform various searches to look for candidate issues:
Random issue (you can use the link in the left sidebar of the bug tracker to go through random issues until you find one that you like
Procedures
The goal of the bug day is to process bug reports in the Python bug tracker, trying to fix and close issues.
What to do:
Grab a copy of the Python codebase from Mercurial, following instructions in the Developer's Guide, and compile it.
If you have a problem that isn't in the bug tracker, announce it to the IRC channel, and if it's more than five minutes' work, create a bug report for it. See the 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.") or on the bug report itself. This avoids accidentally duplicating work.
- Consider providing a patch that fixes the problem, or at least a simple test case that demonstrates the bug. Please see the patch submission guidelines in the Developer's Guide before submitting a patch.
- Does the bug appear to be gone in the Python development version (the Mercurial branch "default", that will become 3.4), but not the 3.2, 3.3 or 2.7 maintenance branchs? Report that, too.
- If someone else has supplied a fix, see if this fix works for² you, and add 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 get committed. The bug tracker has a lot of items in it, and it's easy for bugs to be overlooked.
- Feature requests should be classified as type 'feature request' in the bug tracker.
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 |
2008-02-23 |
48 bugs+patches |
2008-05-10 & 11 |
34 bugs+patches |
2009-04-25 |
|
2010-11-20 & 21 |
|
2012-11-03 |
Preparatory Tasks
- Need to set up log of python-dev channel
- Send announcements (python-announce, python-dev, PSF weblog, personal web log. python-list?)