[Fwd: Re: New bugzilla components.]
-------- Original Message -------- Subject: Re: New bugzilla components. Date: Sun, 16 Dec 2007 18:52:40 -0700 From: James McKenzie <jjmckenzie51(a)sprintpcs.com> To: Dmitry Timoshkov <dmitry(a)codeweavers.com> References: <47640A28.7080701(a)kievinfo.com> <004f01c83f9a$cae2e500$a600fea9(a)DMITRY> <22821af30712152034t1ee5318ai38eba71df919d38f(a)mail.gmail.com> <200712160933.09187.kai.blin(a)gmail.com> <001101c83fcc$2b6cd490$a600fea9(a)DMITRY> Dmitry Timoshkov wrote:
Users are not supposed to set a category the bug belongs to, this requires an investigation and knowledge of a developer. Personally I'd prefer to have "default" in the list instead of "wine-misc".
Better choice: Unknown or intial report. This will allow a user to file a bug without having to get technical. This also allows bug triage and for the appropriate developer or development team to be notified of a new bug. As to listing each and every dll, that would be a mess. Keep it to components and parts and use keywords if necessary to identify offending dlls. James McKenzie
On Dec 16, 2007 7:53 PM, James McKenzie <jjmckenzie51(a)sprintpcs.com> wrote:
-------- Original Message -------- Subject: Re: New bugzilla components. Date: Sun, 16 Dec 2007 18:52:40 -0700 From: James McKenzie <jjmckenzie51(a)sprintpcs.com> To: Dmitry Timoshkov <dmitry(a)codeweavers.com> References: <47640A28.7080701(a)kievinfo.com> <004f01c83f9a$cae2e500$a600fea9(a)DMITRY> <22821af30712152034t1ee5318ai38eba71df919d38f(a)mail.gmail.com> <200712160933.09187.kai.blin(a)gmail.com> <001101c83fcc$2b6cd490$a600fea9(a)DMITRY>
Dmitry Timoshkov wrote:
Users are not supposed to set a category the bug belongs to, this requires an investigation and knowledge of a developer. Personally I'd prefer to have "default" in the list instead of "wine-misc".
Better choice: Unknown or intial report. This will allow a user to file a bug without having to get technical. This also allows bug triage and for the appropriate developer or development team to be notified of a new bug.
What? I assume you're talking about adding a new landing page like a simplified initial bug report. That has nothing to do with the current discussion, so please bring that up out of this thread if you really want that. Also, we already are notified of new bug reports through wine-bugs.
As to listing each and every dll, that would be a mess. Keep it to components and parts and use keywords if necessary to identify offending dlls.
huh? No one said to list each and every dll. I have a feeling you don't quite understand the issue... -- James Hawkins
Dmitry Timoshkov wrote:
Users are not supposed to set a category the bug belongs to, this requires an investigation and knowledge of a developer. Personally I'd prefer to have "default" in the list instead of "wine-misc".
Better choice: Unknown or intial report. This will allow a user to file a bug without having to get technical. This also allows bug triage and for the appropriate developer or development team to be notified of a new bug.
What? I assume you're talking about adding a new landing page like a simplified initial bug report. That has nothing to do with the current discussion, so please bring that up out of this thread if you really want that. Also, we already are notified of new bug reports through wine-bugs.
While wine-bugs can notify us of new bugs, there's not really anyway to search for 'untriaged' bugs. A keyword or a default component would allow for this. Since I spend most of my time attempting to verify/triage new bugs as well as trimming out old bugs, this would be a big help. On a side note, what is the general consensus on an 'unimplemented function' keyword? -Austin
On Dec 17, 2007 12:51 AM, Austin English <austinenglish(a)gmail.com> wrote:
Dmitry Timoshkov wrote:
Users are not supposed to set a category the bug belongs to, this requires an investigation and knowledge of a developer. Personally I'd prefer to have "default" in the list instead of "wine-misc".
Better choice: Unknown or intial report. This will allow a user to file a bug without having to get technical. This also allows bug triage and for the appropriate developer or development team to be notified of a new bug.
What? I assume you're talking about adding a new landing page like a simplified initial bug report. That has nothing to do with the current discussion, so please bring that up out of this thread if you really want that. Also, we already are notified of new bug reports through wine-bugs.
While wine-bugs can notify us of new bugs, there's not really anyway to search for 'untriaged' bugs. A keyword or a default component would allow for this. Since I spend most of my time attempting to verify/triage new bugs as well as trimming out old bugs, this would be a big help.
Bad idea. This would promote inactivity on older bugs. Just pay attention to wine-bugs.
On a side note, what is the general consensus on an 'unimplemented function' keyword?
I'm pretty sure the consensus is against. -- James Hawkins
participants (3)
-
Austin English -
James Hawkins -
James McKenzie