launchpad development|
Size: 4725
Comment:
|
Size: 4676
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 76: | Line 76: |
| * [[https://bugs.edge.launchpad.net/malone/+bug/497414|Yet another checkwatches KeyError]] had conflicts when submitted to pqm. Will need to clean up and resubmit in January. | |
| Line 90: | Line 91: |
| * [[https://bugs.edge.launchpad.net/malone/+bug/497414|Yet another checkwatches KeyError]] (branch ready to land; Deryck to ensure that it lands before holidays start - to be deployed to loganberry as soon as possible, too). |
This page is about the code that runs Launchpad's bug tracker. For information about handling and triaging Launchpad-related bugs, please see BugHandling instead. Ask for help right away if you have any questions. |
Launchpad Bugs is often called malone in code or by Launchpad developers. This is the application responsible for code that handles bugs, filing bugs, bug search, bug watches, external bug tracker integration, bug email, and more.
The developers who work on Malone full time are currently doing development work for the themes and user stories around Launchpad v.4.0.
Themes and User Stories
For general Launchpad info, see Themes and Stories.
The bugs team itself is working on 3 user stories under one general theme.
Getting Bugs "off" Ubuntu
Other stories lined up behind the ones in active development are:
Note: Bug Q&A was under active development but is being delayed due to efforts required to get checkwatches stable. As soon as one of the current stories is done, work on bug Q&A will continue.
In Progress
3.1.12 (December 2009)
Work to be taken up during this cycle (due December 16, 2009) are listed by developer below.
Abel
- better patch display in bug pages [DONE]
Deryck
- Follow up with jml/sinzui about flatter bug link (death to this series nonsense) [TODO]
overlooked. No need to follow up here until Bug Q&A gets closer to development time, given recent changes to focus more on checkwatches.
Gavin
- Display the number of affected users [DONE]
Graham
+filebug async work [DONE]
- One minor UI bug and a possibly related OOPS remain.
- designing bug heat algorithm
- Still TODO. Graham took this over from Deryck and couldn't complete before holiday time.
Tom
Dialog widget for Bug Q&A dialog [TODO]
- This is being bumped to January.
- Tom was CHR until end of year after.
10.01 (January 2010)
The "Bring the Heat" month. Karl Fogel joins our team, and we have a sprint dedicated to finishing a bug heat implementation.
We can divide the work up according to developer when we reconvene in January, though everyone has a good idea by now what stories they drive. 
- Risky bits of bug heat done early
- algorithm code
- cron job (or whatever) to update bug heat
- Sprinting on Bug Heat in week 3
- applying the feature to UI across Launchpad
- applying in search
- Begin work to re-factor checkwatches for reliable bug watch updates
- Close out patch tracking project
- Everything landed by EOC (End of Cycle)
Additional bugs we must fix include:
Bug 357907, +filebug timeout with large blobs
Yet another checkwatches KeyError had conflicts when submitted to pqm. Will need to clean up and resubmit in January.
Ongoing
Zero OOPS
Bug number |
Description |
Developer |
OOPS when updating the details of a bug tracker with a large number of bug watches |
|
|
premature timeout on +filebug pages |
|
Need Investigation
Looks like Bug #433995, but at first glance seems to relate to new inline dupe finder.
