qingqing...@elektrobit.com wrote on 2011-06-14: > > For RELEASED/FIXED bugs: - I recommend all bug reporters check own bugs > and verify the "RELEASED/FIXED" bug within 2 weeks; - If bug reporter > doesn't come back to verify bugs in 2 weeks from now on, QA contact will > help to retest and verify the bugs with comments "verified on behalf of > reporter" added. - If QA contact has difficulty to follow up the > original bug report, and fails to get clarification from reporter, QA > contact will set assign keyword "verification pending" to the bugs. Pls. > help to spread the message to bug reporters and remind her/him if you > notice there is any "RELEASED/FIXED" bug reported by the guy your known. > It is ridiculous that all those bugs are leaving for QA contact to > verify or finally most of them are marked as "verification pending". :) >
Yeah, I agree with Qingqing, we should always give the first chance to reporters to verify their own RELEASED-FIXED bugs. And here, I would also recommend our QA contacts to add some kind comments in bug reports to remind the reporters to verify their bugs before mark them as Verification-Pending, just in case the previous notification of the release slipped reporters' attention. > (2)QA verify > the RESOLVED/FIXED bugs with latest trunk:testing image following the > new bug status change process, meaning "Marked as 'resolved' by > developer -> submitted to Trunk:Testing -> accepted by R.E.-> marked as > 'released' by R.E once the package is in Trunk:Testing." Not recommended > at this moment as still open issues regarding the new process. I believe the open issues mentioned here are those in this thread, :) http://lists.meego.com/pipermail/meego-qa/2011-June/001843.html hope they can be clarified as soon as possible. >(3)QA > verify the RESOLVED/FIXED bugs with latest trunk image directly. > Precondition is the fix is promoted to Trunk. And need clarify if the > bug is not reproduced on the latest trunk image, can the bug status > change from RESOLVED to VERIFIED directly? IMO,(3)is more > straightforward if the fix is definitely prmoted to Trunk. Pls give your > comments freely. I am more interested in the third proposal, it's better if that QA can take more actions regarding these ages RESOLVED/FIXED bugs. :) IMHO, I think we can verify these RESOLVED/FIXED bugs which stay as this status for >= 2 weeks if they are not reproducible with two latest Trunk images : - check with latest Trunk image, if the bugs are not reproducible, then add comments to mention the results of checking and ask release engineers to confirm that the packages have been promoted - if there is still no any response from release engineers, check with next Trunk image, verify the bugs and change status to verified-fixed if they are still not reproducible, and with a clear comments being added. > MeeGo-qa mailing list > MeeGo-qa@lists.meego.com > http://lists.meego.com/listinfo/meego-qa Best Regards, Jason _______________________________________________ MeeGo-qa mailing list MeeGo-qa@lists.meego.com http://lists.meego.com/listinfo/meego-qa
