> Bugs not linked to appdb > by Dan Kegel Nov 26, 2008; 01:02am > > Somebody asked if there was a way to find out which > bugs were not yet linked into the appdb. There > ought to be, but I don't know of one, so I ran > the report the hard way last night. It's at > http://kegel.com/wine/unlinked.html > - Dan Dan, Thank you for running the report (dated: 2008/11/24). Viewed each of 2164 bugs listed in bugzilla and and searched for a corresponding Wine AppDB entry, linking those I could identify (over 500 links created). (Apologies if I made a mistake or typed in a wrong bug number) It was an interesting experience, and found that when people report bugs the following may not be true years later: -That when they state the program is the "latest release", instead give the release or version of the program they are reporting. -Program Names should not be abbreviated in the bug reports. (especially the games!) The last bug on Dans report was "Bug 16203" any bug after this has not been looked at or linked. A number of Bugs had the keyword "NoAppDBEntry" and had a appdb entry linked so that keyword may need to be removed from them. The quality of the bug reports, have convinced me that when I submit a report in the future I will think very carefully about providing as much information as possible. Some reading on Bug triage: - http://www.cs.ubc.ca/labs/spl/projects/bugTriage.html Bug Report Assignment (a.k.a. Sibyl) - http://lostgarden.com/2008/05/improving-bug-triage-with-user-pain.html Improving Bug Triage with User Pain "Display the anchored scales prominently on the UI where bugs are entered" - - Nat
