On Dec 31, 2007 6:10 PM, Maarten Lankhorst maarten@codeweavers.com wrote:
Vijay Kiran Kamuju schreef:
just like last year we did an audit of all the bugs in bugzilla. I think this year also we should do the same, the bugs are growing large and older bugs are being neglected. just wanted to say that we need to check all the old open bugs, and test them/ask the user for status. Close the bug as Abandoned if there is no response. also test the application yourself on latest git. this is the work to be done. and we need volunteers for this work.
need volunteers to clear up the mess(old abandoned bugs) in bugzilla
The situation with bugzilla is quite bad. The rate at which bugs are opened is a LOT higher then the rate of bugs that can be fixed. This adds a lot of bugs that won't ever be fixed.
The situation also isn't helped by the fact that a lot of the newly generated bug reports are not of good enough quality. Example: "My obscure app doesn't do xxx", without for example mentioning what the app is, or a link to a demo, or insufficient information to really reproduce the bug.
I can see the quality of bugs is deteriorating at a fast rate. since it crossed 10K mark. I think we should some things compulsory in the bug reports they are submitting. And we should add a new textbox to bugzilla when creating a new bug. It should be steps to replicate/reproduce the bug. It should be like step1, step 2, ....
The situation isn't improved by the fact that bugs are reopened by those persons after minimal additions. Perhaps we should have a bug moderation? Only allow bugs that follow the criterion, then have a way for bugzilla admins to accept bug reports and then a new bug report entry is created in bugzilla.
Bugzilla moderation is an very daunting task. and on top of it verifying the bugs will add to it. Forwarding abandoned patches in bugzila, asking for reasons, put them in bugzilla. And it needs at least 1-2 persons to work on them full time ;) As its an open source project we cant impose have a full time moderators May be we need to think of an alternate solution. Adding new fields to the bugzilla, that I suggested an be another alternative ;) lets think of more alterntives
-- VJ
-Maarten
On Dec 31, 2007 5:56 PM, Vijay Kiran Kamuju infyquest@gmail.com wrote:
We would be doing this for 1-2 months as the Wine 1.0 release might happen in may be next 6-7 months time. We might expect lotta bugzilla activity as wine goes out of beta. and all the old bugs will be ignored and bugs grow exponentially. There will be lotta bugzilla spam, we cant avoid it ;) Last time it was mostly done by Jonathan Ernst and others, also by me
I've got some spare time/bandwith to do this, but had been holding back to prevent the flood of bugzilla mail. But like you said, this needs to be done before 1.0, so if we're ready to do it now, I'll start triaging a lot more old stuff. I'll wait a day or so to get some more replies before though.
On Dec 31, 2007 6:10 PM, Maarten Lankhorst maarten@codeweavers.com wrote:
The situation isn't improved by the fact that bugs are reopened by those persons after minimal additions. Perhaps we should have a bug moderation? Only allow bugs that follow the criterion, then have a way for bugzilla admins to accept bug reports and then a new bug report entry is created in bugzilla.
-Maarten
Does bugzilla support this? How about not allowing someone without higher bugzilla privileges to reopen bugs?
Austin English wrote:
On Dec 31, 2007 6:10 PM, Maarten Lankhorst maarten@codeweavers.com wrote:
The situation isn't improved by the fact that bugs are reopened by those persons after minimal additions. Perhaps we should have a bug moderation? Only allow bugs that follow the criterion, then have a way for bugzilla admins to accept bug reports and then a new bug report entry is created in bugzilla.
-Maarten
Does bugzilla support this? How about not allowing someone without higher bugzilla privileges to reopen bugs?
It should. Some of the other projects I work on will only allow a person with admin level to change the status of a submitted bug, including re-opening. I would also like to see this with bugzilla, even though I am an ordinary 'user'. This would prevent users from closing a bug report and then opening it again, even if the problem affects a different module. IMHO, these are two separate bugs.
James McKenzie
On Mon, Dec 31, 2007 at 05:49:14PM -0700, James McKenzie wrote:
Austin English wrote:
On Dec 31, 2007 6:10 PM, Maarten Lankhorst maarten@codeweavers.com wrote:
The situation isn't improved by the fact that bugs are reopened by those persons after minimal additions. Perhaps we should have a bug moderation? Only allow bugs that follow the criterion, then have a way for bugzilla admins to accept bug reports and then a new bug report entry is created in bugzilla.
Does bugzilla support this? How about not allowing someone without higher bugzilla privileges to reopen bugs?
It should. Some of the other projects I work on will only allow a person with admin level to change the status of a submitted bug, including re-opening. I would also like to see this with bugzilla, even though I am an ordinary 'user'. This would prevent users from closing a bug report and then opening it again, even if the problem affects a different module. IMHO, these are two separate bugs.
If you know how to configure bugzilla to prevent the bug creator from reopening it, I'd like to hear about it (AFAIK it's not possible). As far as I remember regular users who are not the creator are already disallowed from changing the resolution.
Jan
-
Austin English -
James McKenzie -
Jan Zerebecki -
Vijay Kiran Kamuju