Diff for "Bugs"

Not logged in - Log In / Register

Differences between revisions 28 and 29
Revision 28 as of 2009-12-22 20:16:08
Size: 3783
Editor: deryck
Comment:
Revision 29 as of 2010-01-04 11:55:09
Size: 3963
Editor: gmb
Comment:
Deletions are marked like this. Additions are marked like this.
Line 66: Line 66:
 * [[https://bugs.edge.launchpad.net/malone/+bug/502905|DisconnectionErrors in checkwatches]]. Waiting for other bug fixes to be CP'd before deciding how problematic this bug is.

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

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:

Ongoing

Zero OOPS

Bug number

Description

Developer

447100

OOPS when updating the details of a bug tracker with a large number of bug watches

495463

premature timeout on +filebug pages

Need Investigation

Other backlog queues

Historical dashboard notes

Bugs (last edited 2010-06-07 16:49:22 by deryck)