Ubuntu30 Mar 2009 01:49 pm

Now that the final release of Jaunty Jackalope is rapidly approaching, it is important that we keep on top of Jaunty bug reports. To aid in doing this I’ve created a bug report that includes bug tasks created since the Beta was released.

The report only includes bug tasks that are in a New or Complete status using the theories that the bug is missing information if it is Incomplete and somebody who knows what they are doing looked at it if it is Triaged. The report also includes a new feature I’ve been toying with – bug gravity. The bug gravity is an attempt to determine which bug reports should be looked at first based off properties of the bug like who reported it, tags, number of subscribers, number of duplicates, numbers of users affected and whether or not it is private. The legend for how gravity is computed appears at the bottom of the report. Another thing I added was information about what component a package appears in – you can see it by mousing over the package name.

I’ve also added the script, bugs-since-sometime.py, that generates the report to the ubuntu-qa-tools project in case you want to see bugs since some date. I plan on modifying the date criteria for the report after the release candidate comes out.

3 Responses to “Bug tasks since Beta”

  1. on 30 Mar 2009 at 3:12 pm Jacob

    Bugreports AND fixing is indeed important. I’ve growing increasingly frustrated with Ubuntu in that department (got feedback 13 months after reporting a issue).

    I’m testing Jaunty beta at the moment, and my view is that 9.04 is the most promising Ubuntu release since 7.10. It’s the most flawless install I’ve ever had with Ubuntu. If that is followed up by addressing bugs when issues arise it will become a winner. I might even start recommending Ubuntu to newbies again.

  2. on 30 Mar 2009 at 4:26 pm Greg

    Awesome list, Brian.

    I especially like being able to sort that list by the various attributes; very handy.

    I think you need a new title, though, Brian. “Bug Master” isn’t sufficient any longer. How about “Bug List, Chart, and Graph Master” ?

  3. on 30 Mar 2009 at 11:24 pm tricky1

    Imho Canonical still does not have the resources required for producing usable releases each semester.
    So all your best efforts will evaporate because

    a) Some people do no longer report bugs because most of time it is a waste of time

    b) Those that still do report immediately produce an unmanageable load. Your beautifuly new list is proof of it ;-(

Feed on comments to this Post

Leave a Reply