Diff for "Bugs"

Not logged in - Log In / Register

Differences between revisions 1 and 25 (spanning 24 versions)
Revision 1 as of 2009-07-22 08:38:20
Size: 171
Editor: allenap
Comment:
Revision 25 as of 2009-12-22 20:06:08
Size: 4697
Editor: deryck
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Bugs = ||<tablestyle="width: 100%;" colspan=3 style="background: #2a2929; font-weight: bold; color: #f6bc05;">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. [[Help|Ask for help]] right away if you have any questions. ||
Line 3: Line 3:
Often referred to in the code as `malone`. ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||
Line 5: Line 5:
 * [[https://launchpad.net/malone|Launchpad project page]] 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.
Line 7: Line 7:
 * [[/ExternalBugTrackers|External Bug Trackers]]  * [[/Dashboard411|How to use this wiki page]]
 * [[/Contributing|Interested in contributing or learning more?]]

The developers who work on Malone full time are currently doing development work for the themes and user stories around [[VersionFourDotO|Launchpad v.4.0]].

= Themes and User Stories =

For general Launchpad info, see [[VersionFourDotO/Themes|Themes]] and [[VersionFourDotO/Stories|Stories]].

The bugs team itself is working on 3 user stories under one general theme.

== Getting Bugs "off" Ubuntu ==

 * [[Bugs/BugHeat|Bug Heat]]
 * [[Bugs/ReliableBugSyncing|Reliable Bug Syncing]]
 * [[Bugs/PatchTracking|Patch Tracking]]

Other stories lined up behind the ones in active development are:

 * [[Bugs/BugQ&A|Bug Q&A]]

'''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. Deryck will ping sinzui before holiday if time allows. Will need to be picked up again in 2010.

=== Gavin ===
 * Display the number of affected users [DONE]

=== Graham ===
 * [[https://bugs.edge.launchpad.net/malone/+bugs?field.tag=story-ajaxify-dupe-finder|+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:

 * [[https://bugs.edge.launchpad.net/malone/+bug/357907|Bug 357907]], +filebug timeout with large blobs

= Ongoing =

== Zero OOPS ==

||<tablestyle="width: 100%; text-align: center;">Bug number || Description || Developer ||
|| [[https://bugs.edge.launchpad.net/malone/+bug/447100|447100]] || OOPS when updating the details of a bug tracker with a large number of bug watches || ||
|| [[https://bugs.edge.launchpad.net/malone/+bug/495463 |495463 ]] || premature timeout on +filebug pages || ||

=== Need Investigation ===

 * [[https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1450A1714|OOPS-1450A1714]]
    * Looks like [[https://bugs.edge.launchpad.net/malone/+bug/433995|Bug #433995]], but at first glance seems to relate to new inline dupe finder.
 * [[https://bugs.edge.launchpad.net/malone/+bugs?field.tag=oops|Backlog of OOPS work]]
 * [[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).



== Other backlog queues ==

 * [[https://bugs.edge.launchpad.net/malone/+bugs?field.tag=bug-page|Bug page bugs]]
 * [[https://bugs.edge.launchpad.net/malone/+bugs?field.tag=post-3-ui-cleanup|Remaining post-3.0 UI bugs]]

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. Deryck will ping sinzui before holiday if time allows. Will need to be picked up again in 2010.

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:

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

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