On Saturday 11 April 2009 10:58:43 am jdd wrote:
Carlos E. R. a écrit :
But the bugzilla screening team could know that and reasign.
it's obviously there that things break: somebody (or any automated tool) should scan the bugs for activity.
I guess that you can create such reports with reporting tools that already exist in bugzilla.
Any people with some bug assigned should have a priority sorted list and activity flag (if somebody is busy, better assign the bug to an other people)
I guess that they already work that way, though reassigning is not that easy. All developers can read program code, but there is a lot of other knowledge that one developer must have in order to understand what the code is doing. You can't simply assign Xorg specialist to fix kernel issue, and vice versa. There are things they can do on other projects, but this has it's limitations.
most bugs have to be worked on very fast, because the user have to use it's computer and it's more and more difficult to find what happen when time passes (most bugs I see are difficult to reproduce)
I agree that fast reaction is very important, otherwise you get opened bugs that reporter doesn't care anymore. There are whole classes of configuration, UI and usability issues that user can find work around on its own and quit cooperation on the bug.
this don't mean it's easy to setup :-(,
It could be very easy to create reasonable workflow, bigger problem would be to get people involved. (nothing new)
but it's why the mailing list is often better than bugzilla: answers are most of the time given in minutes when bugzilla answers in days or weeks
That is why we need shim layer between ML and forums, and developers, so that they can save time, now used to scan mail lists, for something that other can't do. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org