I think that Bugzilla could have an option to join all issues that are related to an specific application. For example, if someone is testing Oblivion, there should be a place where we can relate every issue that is happening to Oblivion. So, instead of filing a new entry on Bugzilla, people could only add another issue to an application. In this way, people can provide more info about an application and developers can follow the behavior of applications on different wine versions. This will also reduce the amount of entries that appear on Bugzilla. An advantage of this is that should be possible to wine users automatically submit their execution logs. This would help increase the amount of valuable data to the developers.
On Fri, 2010-08-20 at 15:45 -0500, fernandocarvalho wrote:> I think that Bugzilla could have an option to join all issues that are > related to an specific application. > For example, if someone is testing Oblivion, there should be a place > where we can relate every issue that is happening to Oblivion. >That's already in place and only depends on clued-up users: - search for similar bugs FIRST - if there is already one filed, add a comment to it. Raise a new bug ONLY if you can't find a related one. If you don't look for similar bugs before raising a new one then YOU ARE THE PROBLEM. From looking at the Bugzilla 'bug report changes' emails about bugs I've raised it appears that most people are too stupid to search existing bugs before raising a new one. Martin
fernandocarvalho wrote:> I think that Bugzilla could have an option to join all issues that are related to an specific application. > For example, if someone is testing Oblivion, there should be a place where we can relate every issue that is happening to Oblivion.That's what the AppDB is for, and you can add bug links there.> > So, instead of filing a new entry on Bugzilla, people could only add another issue to an application. > In this way, people can provide more info about an application and developers can follow the behavior of applications on different wine versions. >I think you don't understand how the process works. Wine developers don't usually follow whole applications, they tend to specialize in specific areas of the code, and work on bugs that fall in their area of expertise. A single application may be affected by multiple bugs in completely unrelated parts of the code, while a single bug may affect multiple apps. Lumping together unrelated bugs into one big "this app doesn't work right" bug while requiring separate reports for each app affected by the same bug would not be helpful to the people who actually fix bugs.