Hi, You have good points here. Thanks for feedback. I didn't think the fact that any of MeeGo user can and hopefully also files bugs, not just testers. From now on I will pay more attention how to add comments and how to ask verification. Your example was very good.
Br, Iekku >-----Original Message----- >From: ext Andre Klapper [mailto:[email protected]] >Sent: 12 January, 2011 11:56 >To: [email protected] >Cc: Huttunen Iekku (EXT-Ixonos/Tampere) >Subject: Bug verification request comment style > >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] >> Subject: [MeeGo Platform - Bug 11320] touchpad on Lenovo s10-3t >doesn't work well >> >> http://bugs.meego.com/show_bug.cgi?id=11320 >> >> --- Comment #2 from iekku <[email protected]> 2011-01-10 >22:59:18 PST --- >> QA contact or reporter, please verify this asap. > > >Hi Iekku and everybody, > >I don't like this comment style. It might work nowadays but it won't >work anymore once we have more real users in Bugzilla. > >I imagine to be an average MeeGo user that reported a bug and I receive >such a comment via bugmail. > >It was already a big step to voluntarily file a bug report, to provide >more debug information according to the steps provided in a follow-up >comment by a triager, and to not give up on the way. > >Many users never ever file a report because it takes time, it often >takes follow-up time, and bugtrackers look veeeery scary. > >If I'm now even asked to verify this in a bit of a pushy tone I might >refrain from filing more reports. >"asap" is probably the "ASAP" that I can find via Google, as I don't >have English as my mother tongue? ;-) > >For bug 11320 I don't see much sense in verifying a duplicate. > >Is this kind of comment also added to reports closed as FIXED? >If yes: > I'd have no idea how to "verify asap" - I run my stable MeeGo > version, I don't know to install your unstable version that > includes the fix, and "unstable" sounds scary if that term is > mentioned at all between the version numbers (can't find an > example right now). > >In bugs.maemo.org I've used the following comment: > "A future public update [...version info...] will include the > fix. > Please verify that this new version fixes the bug by marking > this bug report as VERIFIED after the public update has been > released and if you have some time." > >As http://wiki.meego.com/Bugzilla/how-report-bugs only vaguely mentions >"QA or Bug Submitter verifies bug fixing" but nothing about nagging, I >favor the idea of agreeing on some "default comment template" for >certain common actions. > >Let's be nice to folks that file bug reports - the number of paid >reporters (QA) will decrease once MeeGo becomes popular. > >Comments? > >andre >-- >Andre Klapper (maemo.org bugmaster) _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
