Ben Klein wrote on May 4th:
Final post from me.
2009/5/5 Nicklas Börjesson Nicklas.Borjesson@ws.se:
b) I thought that priority was developer priority and severity was severity for the users.
Nope. Both for the benefit of developers, hence why they're both on bugzilla.
One question: Does Bugzilla have a place for user's to place the Impact on their ability to use a Windows program? This is much different than the priority and severity fields.
James McKenzie
James Mckenzie wrote:
One question: Does Bugzilla have a place for user's to place the Impact on their ability to use a Windows program? This is much different than the priority and severity fields.
Yes, here: http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity
2009/5/4 James Mckenzie jjmckenzie51@earthlink.net:
Ben Klein wrote on May 4th:
Final post from me.
2009/5/5 Nicklas Börjesson Nicklas.Borjesson@ws.se:
b) I thought that priority was developer priority and severity was severity for the users.
Nope. Both for the benefit of developers, hence why they're both on bugzilla.
One question: Does Bugzilla have a place for user's to place the Impact on their ability to use a Windows program? This is much different than the priority and severity fields.
No, but it is not important for bugzilla. That information belongs in the AppDB, which allows for this, with the application ratings.
Roderick Colenbrander and I were talking about the severity levels on irc the other day. We tried to outline the existing severity process that seems to be in use (not what is neccesarily listed in bugzilla) and came up with the following levels of bug severity:
* normal * major (release level, e.g. dib engine, 64 bit support, usb, etc) * blocker (compile failure, severe wine crash, system crash due to triggering driver bugs)
As far as I can see that's what the current usage of serverity is in bugzilla.
Other thoughts during our discussion were that perhaps assignee should be the one that can change the severity rather than reporter.
Cheers, --John Klehm
On Mon, May 04, 2009 at 02:39:28PM -0500, Austin English wrote:
2009/5/4 James Mckenzie jjmckenzie51@earthlink.net:
One question: Does Bugzilla have a place for user's to place the Impact on their ability to use a Windows program? This is much different than the priority and severity fields.
No, but it is not important for bugzilla. That information belongs in the AppDB, which allows for this, with the application ratings.
It'd be handy if bug links in AppDB allowed some kind of indication of the problem it causes or at least the severity thereof.
I've got a whole bunch of bugs linked from Warhammer Online which have really unuseful bug titles, causing readers of the page to end up reporting the same things in the comments.
There's prolly an issue as well in the bug report naming, it seems that Wine doesn't have a strong culture of renaming bugs when they've been diagnosed. (Bug 13335 is a good example of this, I feel. A user pointed out to me the other day that he wasn't running Warcraft 3 when I suggested that it was the problem he was having. There's another bug which refers specifically to Steam in the bug title.)
I've added a Note to the WAR AppDB page which describes symptoms and ties them to linked bugs to try and alleviate this, but it'd be nice if the disconnect wasn't there.
2009/5/5 Paul TBBle Hampson Paul.Hampson@pobox.com:
I've got a whole bunch of bugs linked from Warhammer Online which have really unuseful bug titles, causing readers of the page to end up reporting the same things in the comments.
Bug titles can and should be changed.
2009/5/6 James Mckenzie jjmckenzie51@earthlink.net:
Since the severity and priority fields are developer only, they should not be present.
Developers use bugzilla too. Any restriction we put on casual users will affect experienced users, unless there is some flag in each user's profile for whether the fields will be visible.
Big question is, is it THAT much of a problem? I vote no.
2009/5/6 Rosanne DiMesio dimesio@earthlink.net:
This allows the user to provide input and allow the triage team to provide feedback to the user as well as assign appropriate severity and priorities to bug reports.
There's already a field that does exactly that: the description. It allows users to describe the problem in as much detail as they wish, including its impact, and unlike a drop-down list, is not limited to common issues. I don't see what an additional field to repeat this information in vague terms will do to help anyone.
+1. Also note that vague or misleading descriptions are common, users often don't respond to bugs with more information, and in extreme cases, bugs get closed due to a lack of activity. Adding a field that basically says "it's broken" (in a variety of weird and wonderful ways) won't help with improving descriptions.
On Mon, May 04, 2009 at 11:24:58AM -0700, James Mckenzie wrote:
Ben Klein wrote on May 4th:
Final post from me.
2009/5/5 Nicklas Börjesson Nicklas.Borjesson@ws.se:
b) I thought that priority was developer priority and severity was severity for the users.
Nope. Both for the benefit of developers, hence why they're both on bugzilla.
One question: Does Bugzilla have a place for user's to place the Impact on their ability to use a Windows program? This is much different than the priority and severity fields.
James McKenzie
In catching up on this long discussion, this is the first post that I've seen that actually comes close to pin-pointing what is being requested.
Current: Severity = messure of bug impact on wine
Requested: Severity = message of bug impact on application running in wine
IMHO the bugzilla severity field is not the right place to measure impact to other applications of bugs in the current development. Attempting to track that type of information in the severity field will always lead to confusion and problems.
A more logical approach would be to either add a different field or use tags to track the impact on the affected app.
On Tue, May 5, 2009 at 9:42 AM, Darragh Bailey felix@compsoc.nuigalway.ie wrote:
In catching up on this long discussion, this is the first post that I've seen that actually comes close to pin-pointing what is being requested.
Current: Severity = messure of bug impact on wine
Requested: Severity = message of bug impact on application running in wine
IMHO the bugzilla severity field is not the right place to measure impact to other applications of bugs in the current development. Attempting to track that type of information in the severity field will always lead to confusion and problems.
A more logical approach would be to either add a different field or use tags to track the impact on the affected app.
Again, bugzilla is a developer's tool.
That sort of information belongs in the AppDB, not bugzilla.
-
Austin English -
Ben Klein -
Darragh Bailey -
James Mckenzie -
John Klehm -
Ken Sharp -
Paul TBBle Hampson