Bug Links to wine appdb

NN · Post by NN » Mon Nov 24, 2008 7:33 pm

I would like help with the steps required to create a report of bugs that are not linked to the wine appdb.

If possible can that report be added and selected from the bugzilla intro page.

Thank you
Nat

PS: Are the following email addresses monitored:
bugs-admin @ winehq.org ( Email WineHQ Bugzilla Administrator )
appdb @ winehq.org ( Email your suggestions for improving the AppDB )

Vincent Povirk · Post by **Vincent Povirk** » Mon Nov 24, 2008 10:31 pm

Do you want to file a new bug or link an existing bug to an appdb page?

Only an application maintainer can link bugs to applications. Either
file a comment asking the current maintainer to do it, or apply to
become a maintainer.

Vincent Povirk

NN · Post by NN » Mon Nov 24, 2008 11:48 pm

I do not want to file a new bug. I am a application maintainer and I have been linking bugs.

In Bugzilla I have been trying to create a report that will show me existing bugs that do not have existing links to the Wine AppDB

For example see bug 12874 and you will see (AppDB: Show Apps affected by this bug) selecting this link shows a list of applications in the wine appdb that are related to the bug.

I would like a bugzilla report that excludes bugs that have an existing wine appdb link/list?

Is it possible?

Vincent Povirk · Post by **Vincent Povirk** » Tue Nov 25, 2008 12:02 am

It's not possible from bugzilla. The links are apparently stored in
the appdb. I think you would need access to the appdb database to do
this.

Alexander Nicolaysen S... · Tue Nov 25, 2008 8:47 am

On Tuesday 25 November 2008 01:33:47 NN wrote:

I would like help with the steps required to create a report of bugs that
are not linked to the wine appdb.

If possible can that report be added and selected from the bugzilla intro
page.

Thank you
Nat

PS: Are the following email addresses monitored:
bugs-admin @ winehq.org ( Email WineHQ Bugzilla Administrator )
appdb @ winehq.org ( Email your suggestions for improving the AppDB )

[email protected] is sort of monitored, but mail has a tendency to get lost
(or, rather, forgotten). It's not like we ignore mail on purpose, but
sometimes it may seem like we do.

If you don't get an answer within a few days, feel free to send the mail
again.

Alexander N. Sørnes

NN · Post by NN » Sun Nov 30, 2008 3:18 am

Alexander Nicolaysen S... wrote:On Tuesday 25 November 2008 01:33:47 NN wrote:
PS: Are the following email addresses monitored:
bugs-admin @ winehq.org ( Email WineHQ Bugzilla Administrator )
appdb @ winehq.org ( Email your suggestions for improving the AppDB )

[email protected] is sort of monitored, but mail has a tendency to get lost
(or, rather, forgotten). It's not like we ignore mail on purpose, but
sometimes it may seem like we do.

If you don't get an answer within a few days, feel free to send the mail
again.

Alexander N. Sørnes[/quote]

Ok I will, Thank you

NN · Post by NN » Sun Nov 30, 2008 3:45 am

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 ... -pain.html
Improving Bug Triage with User Pain
"Display the anchored scales prominently on the UI where bugs are entered"
-

-
Nat

Post by **dimesio** » Sun Nov 30, 2008 9:30 am

NN wrote: 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!)

Ideally, people should create the links themselves when they file the bug report. Unfortunately, this can't be done directly from bugzilla, and many people forget/don't bother.

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.

The wiki has some clear instructions: http://wiki.winehq.org/Bugs

NN · Post by NN » Sun Nov 30, 2008 4:55 pm

[quote="dimesio"]
Ideally, people should create the links themselves when they file the bug report. Unfortunately, this can't be done directly from bugzilla, and many people forget/don't bother.
[quote]

Ideally yes.

Another issue is that for the Wine Project, Bugzilla the AppDB and wiki and the forum all have separate non logins, which to a lot of people is a hurdle in itself.