On Fri, Apr 27, 2012 at 10:09, Per Jessen <per@computer.org> wrote:
This thread is from -factory, but it applies to the project overall:
Christian Boltz wrote:
Bugzilla is overpowered, I have issues without attention for years.
In theory, yes, all issues probably should go via bugzilla. In practice, I know we don't work like that and that's why I said its worth discussing. We need to think about how we want to work.
What about "force developers to read bugzilla mails/work on their buglist regularly"? ;-)
Bugreports getting dusty is a real problem, and I'd love to present a nostrum how to fix that if I had one.
I second that. The worst problem I have here is when someone picks up an ancient (>6 months old) bugreport and asks me for diagnostics , "could you try <something>?" or "please try with latest version". If I'm lucky, I'll remember which system, which configuration and which softeware I was testing, but more often than not, the system has gone into production, has been reconfigured for something else or is being used by somebodyelse.
I'm considering simply closing my old reports as "CANTFIX" due to "NORESOURCES".
This isn't unique to openSUSE. Most project Bugzillas are overwhelmed. Small number of people trying to deal with a large workload. Once the bug reporting system is overwhelmed, it's hard to keep up... or recover (I'm thinking of the OOo Bugzilla as an example where there were bugs open for 4, 5, or even 6 years or more). Just some thoughts that are passing through my mind... Is anyone assigned to triage all incoming bug reports or do we rely on an automated system? Does someone take the time to actually read each bug report and validate it in some way before it's dumped on a maintainer's doorstep... make sure it has useful information, log files etc? If not, it would be a good opportunity for someone, or several someones, who is/are not a skilled developer to step up and contribute. Does anyone comb through the (old) open bug reports after a release and flag them? Does every bug report have a milestone set? A realistic milestone? What happens if the milestone passes and the bug is still open? Are there bug reports open for more than some arbitrary period (say 6 months, and yes, I know, there are bugs that have been open for several years.. it's a rhetoric question)? Can someone wade through the bug reports older than X months (for some value of X), and for any that are not obviously in process, ping the reporter (or maybe owner) to see if they are still valid/required (without it becoming a spam-fest for the maintainer)? Does any one maintainer have a disproportionate number of open bugs that are not getting attention? (not to say someone is slacking, but that they have way more than they can deal with due to workload, time, effort required ect.) C. -- openSUSE 12.1 x86_64, KDE 4.8.2 -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org