On Tue, 03 Sep 2013 08:48:30 +0200 Jiri Srain wrote:

On 09/02/2013 07:54 PM, Josef Reidinger wrote:

...

Hi, I found quite annoying to have as default assignment bugzilla screening team, that are quite ineffective, which usually result in ask for logs and then assign to yast-maintainers or random people. Annoying part is that it usually takes some time, so if something is broken, we get bug report too late ( usually one release after, so if bug found in M2, we can fix it in M4 ). I think it will be better to have directly as default assign yast-maintainers, so we can quickly proceed to proper developer. I found it especially important for bug reports from factory or next opensuse releases.

Is there any reason to have bugzilla screening team? any opinions?

Well, the reason is to have the bug queue processed before it reaches the team (and offload some of the work from the YaST team). However, I agree that misassignments happen quite often.

Therefore, we indeed have an option to reassign to yast-maintainers. Since we only have one component for YaST in bzilla, we cannot have more fine-grained default assignees.

Jiri

So to raise topic again, when I go thrue bugs for yast component I see from bug activity that there is four scenarios 1) bug sits still on screening team without activity ( not so often, but first reaction is usually ) or return to screening team when bugzilla resign back to default component - this bugs are usually lost or have big delays => big problem my quick query shows 80 bugs for os12.3 and 2 open for bugzilla screening and 6 duplicates closed when assigned to screening team - only one actually closed by screening team. 2) bug is correctly assigned to developer ( not so often ) 3) bug is set to yast-maintainers and then move forward ( around 40% ) 4) bug is set to bad maintainer and he reassign to correct one ( around 40 % ) So my conclusion is that screening team helps with getting y2logs and very rarely see duplicate. On other side screening team cause delays in bug forwarding ( usually around one weak, which is quite annoying for opensuse ), additional work when assign to wrong person. When I see how often things happen I think that it more often cause problem then helps, so from my POV it make sense to set yast component to yast-team screening, autoyast to autoyast maintainer and installation to yast-team screening. Any comments, counter-proposals or different opinions? Or own experience with bugzilla screening team? Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org

Dne 25.9.2013 09:22, Josef Reidinger napsal(a): [...]

So my conclusion is that screening team helps with getting y2logs and very rarely see duplicate.

I agree with that, they help with requesting y2logs, but they quite often do not see a duplicate. (But to be fair, sometimes it is hard to find a duplicate without analyzing the logs or knowing some Yast internals, so that's OK.)

On other side screening team cause delays in bug forwarding ( usually around one weak, which is quite annoying for opensuse ), additional work when assign to wrong person.

Yes, I have checked several bugs and it is about 5 days in average, but in some cases it was even 2 weeks. So far it has not caused any problems for me as the bugs were not critical. (And critical bugs from Coolo went to me very quickly ;-)) But this can be a problem in RC phase, when we could miss some bug reports which could be fixed in GM.

When I see how often things happen I think that it more often cause problem then helps, so from my POV it make sense to set yast component to yast-team screening, autoyast to autoyast maintainer and installation to yast-team screening.

I'm fine with this proposal. -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org