ubuntu-defect-analysts team mailing list archive

[Kate Stewart <kate.stewart@xxxxxxxxxxxxx>]

Ursula, Pedro, Joseph, Jose, 
   I'm doing a pass through the escalated and "needs to be" escalated
bugs right now, and want to make sure there are no others from the
defect analysts that should be considered.   Here's what I have so far
from the defect analysts needs.  (thanks Brian!).  Anything other bugs
on each of your top "need a fix to this launchpad bug to make my life a
bit more sane list?"  or does the list Brian provided hit your top ones
as well?

Currently escalated bugs, and those that are being considered to be
escalated can be found here:
https://wiki.ubuntu.com/Launchpad/Stakeholder/UbuntuEngineering

Thanks, 
Kate 

On Wed, 2011-10-19 at 15:19 -0700, Brian Murray wrote:
> LP: #605293 - bug watches for archived debian bug reports appear not
> to exist
>     They are actually showing up as Fix Released now which is wrong
> and makes it very hard to tell from what set of bugs we may be able to
> find a fix upstream.

> LP: #846003 - janitor shouldn't blindly set duplicate bugs to Fix
> Released
>     I found about 232 cases where the janitor, using changelog info,
> set a duplicate bug to Fix Released.  That's 232 less bugs!  Really
> the janitor knows or can know whether or not a bug is a duplicate and
> should do something smarter.

> LP: #456502 - bug to question not available in the API
>     You have to use the web interface to convert a bug to a question
> and converting a bug to question would be useful for enforcing a
> minimum bug quality.

> 
> LP: #29713 - bug search fails to find results despite exact search
> string being in bug titles

> LP: #878532 - findSimilarBugs() in the Launchpad API returns strange
> things
>     Both of these bugs are important to me for the same reason.  I
> suspect we have lots of duplicate bug reports in Launchpad and it
> would be useful if the text searching within and using Launchpad
> returned relevant results.