Hi! +1 to Andre's post.
And my 1,5 cents to Qingqing's mail about leaving bugs to QA contact: I want to remind what was earlier mentioned on this mailing list, so here's quote from Eric's mail [1]: "The basic role of QA from bugzilla product/component administration is simply to actively follow-up. Making sure the bug is attended properly, ping the default assignee or assignee or reporter to get visibility and comments on the progress, triage bugs, verify and close them whenever possible." Yanshuang Zheng has done good work as a QA contact and pinging issues. We need more as active QA contacts as she is. I hope these mail conversations works as reminder for the QA contacts. What reminds me about the fact that there might be QA contacts and default assignees who aren't anymore working with/for MeeGo. Maybe it's time to check that the information is correct? Br, Iekku [1] http://lists.meego.com/pipermail/meego-qa/2011-June/001884.html >-----Original Message----- >From: meego-qa-boun...@lists.meego.com [mailto:meego-qa- >boun...@lists.meego.com] On Behalf Of ext Andre Klapper >On Tue, 2011-06-14 at 07:41 +0300, qingqing...@elektrobit.com wrote: > >> It is ridiculous that all those bugs are leaving for QA contact to >> verify or finally most of them are marked as "verification pending". >:) > >Maybe ridiculous for people that are paid to work on MeeGo, but not >for average users. >Average users already did spend a significant amount of their free time >to write up the report, submit it, and answer followup questions. >They could have also NOT done it. >Verifying by downloading a new version and installing it is even >several magnitudes more complicated than fiddling with Bugzilla. > >andre _______________________________________________ MeeGo-qa mailing list MeeGo-qa@lists.meego.com http://lists.meego.com/listinfo/meego-qa
