All, I believe this is kind of “people not following process” issue instead of bugzilla infrastructure issue.
I could share you the experience about how to handle the testability issues in general: Usually after posting comments to describe the testability problems, QA owner will remind features’ reporters that several features are pending for their clarification (considering bugzilla’s automatic notification might be ignored). Some features will got clarified offline, and if not, QA owner will schedule meetings with features’ reporter to discuss those features and get clarification. Actually most features’ testability problem got resolved this way. For ofono, it’s an exception. Even though QA owner has tried the above steps, we still failed to get good clarification to improve the features’ testability, and IMHO the reason is that the features came from diverse sources and sometimes reporter or PM lack the expertise to answer those in-depth technical questions. Per my previous discussion with communication PM , he agreed with invite ofono dev to post their understanding of the features and answer testability questions. Nicolas and Yann, let’s check with communication PM about the progress and schedule meetings with him and ofono dev. Thanks, Fan From: meego-qa-boun...@lists.meego.com [mailto:meego-qa-boun...@lists.meego.com] On Behalf Of Paccou, Nicolas Sent: Friday, May 06, 2011 8:15 PM To: Argotti, Yann; MeeGo-qa@lists.meego.com Subject: Re: [Meego-qa] Bugzilla issues Hi Yann, Yes, I think it could be a good solution to discuss issues I have listed and solve most of them. We could also have a quick feedback for clarifications/review requests by that way. Best regards, Nicolas From: Argotti, Yann Sent: Friday, May 06, 2011 1:44 PM To: Paccou, Nicolas; MeeGo-qa@lists.meego.com Subject: RE: [Meego-qa] Bugzilla issues Hi Nicolas and all, These issues are indeed important to be solved since they have direct impact on our work / contribution effort on the project. I am not really convinced that sending reminder notification is the ultimate solution here for many reasons, likes the ones that Nicolas is stating. I think, since these issues are mainly related to features, we should have some “feature scrub” likes the frequent “bug scrub”. Having right people online on IRC channel at one scheduled time to communicate and review features in Featurezilla should be more efficient to resolve the remaining issues. Do we have such “Feature scrub” in place (or may be this feature topic is already part of some of the bug scrubs) ? If yes, so we must attend them and add to agenda these issues. If not, we should get PM to help setup them. Don’t you think? Thanks, Yann From: meego-qa-boun...@lists.meego.com [mailto:meego-qa-boun...@lists.meego.com] On Behalf Of Paccou, Nicolas Sent: Tuesday, May 03, 2011 12:10 PM To: Andre Klapper Cc: MeeGo-qa@lists.meego.com Subject: Re: [Meego-qa] Bugzilla issues Hi Andre, Thanks for having answered on this topic. I have already done the action you propose but without any result. Reminding the process in Bugzilla is useless for several reasons: - As people often not even read the notifications received by Bugzilla, they still not read the reminder you will send to them - I think the problems I described are not only for oFono features but for all components’ features. Contacting one by one all the people doing wrong operations will not be efficient. I think we need to find a better solution to resolve all Bugzilla issues I described. Best regards, Nicolas -----Original Message----- From: Andre Klapper [mailto:aklap...@openismus.com] Sent: Monday, May 02, 2011 8:08 PM To: Paccou, Nicolas Cc: MeeGo-qa@lists.meego.com Subject: Re: [Meego-qa] Bugzilla issues On Mon, 2011-05-02 at 13:23 +0100, Paccou, Nicolas wrote: > I have noticed several issues that makes difficult/slows down my work. > I request your help in order to find a solution to solve them. > Please find below the first issue that is related to Bugzilla itself. > I wonder if there is a way to ameliorate the situation on this ? The issues all look like targeting people's behavior instead of technical quirks, so the way to go might be telling people in each case in the bug report. andre -- Andre Klapper (maemo.org bugmaster) http://www.openismus.com --------------------------------------------------------------------- Intel Corporation SAS (French simplified joint stock company) Registered headquarters: "Les Montalets"- 2, rue de Paris, 92196 Meudon Cedex, France Registration Number: 302 456 199 R.C.S. NANTERRE Capital: 4,572,000 Euros This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. --------------------------------------------------------------------- Intel Corporation SAS (French simplified joint stock company) Registered headquarters: "Les Montalets"- 2, rue de Paris, 92196 Meudon Cedex, France Registration Number: 302 456 199 R.C.S. NANTERRE Capital: 4,572,000 Euros This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
_______________________________________________ MeeGo-qa mailing list MeeGo-qa@lists.meego.com http://lists.meego.com/listinfo/meego-qa
