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