ReleaseEngineering:PyCon2010: Difference between revisions
Jump to navigation
Jump to search
Lukasblakk (talk | contribs) |
Lukasblakk (talk | contribs) |
||
| Line 7: | Line 7: | ||
==Dev Sprints - Possible Bugs== | ==Dev Sprints - Possible Bugs== | ||
The developer sprints give us an opportunity to work with the Python programming community, both experienced and new developers, on projects that currently aren't getting enough love from the | The developer sprints give us an opportunity to work with the Python programming community, both experienced and new developers, on projects that currently aren't getting enough love from the RelEng team. | ||
PyCon's [http://us.pycon.org/2010/sprints/call-for-projects/ Call for Sprints] will get you inspired to come up with ideas for how Mozilla's Release Engineering team can get involved and get the most out of these days. | PyCon's [http://us.pycon.org/2010/sprints/call-for-projects/ Call for Sprints] will get you inspired to come up with ideas for how Mozilla's Release Engineering team can get involved and get the most out of these days. | ||
Please add any bugs here that you think | Please add any bugs here that you think could use a developer sprint: | ||
{| class='sortable' style="border:1px solid black" border="1px" | {| class='sortable' style="border:1px solid black" border="1px" | ||
Revision as of 22:33, 7 January 2010
PyCon 2010
PyCon is the largest annual gathering for the community using and developing the open-source Python programming language. This year's conference includes 2 days of tutorials before the conference and 4 days of developer sprints post-conference.
Attending
- catlee
- lsblakk (Feb 17th - 25th)
Dev Sprints - Possible Bugs
The developer sprints give us an opportunity to work with the Python programming community, both experienced and new developers, on projects that currently aren't getting enough love from the RelEng team.
PyCon's Call for Sprints will get you inspired to come up with ideas for how Mozilla's Release Engineering team can get involved and get the most out of these days.
Please add any bugs here that you think could use a developer sprint:
| Bug # | Description | Level of difficulty | Point person |
|---|---|---|---|
| bug 475902 | buildbot's "Stop build" doesn't work for unit test, aborts current test only | low to medium |