Hi Srikanth, This is good point. I am suggesting the rule to be: If there is a bug which was logged in the earlier releases, and in the latest release it is not reproducible, reporter or QA should leave a comment to indicate that the issue is not reproducible, specify the image information, device information and package information, and ask bug owner if he/she agrees the bug has been fixed. In good situation, bug owner will comment that bug so that we could handle the bug based on comments. If bug owner doesn't respond, the bug would be retested a week later and if it's still not reproducible, the bug could be "VERIFIED-FIXED".
Make sense to you? Thanks, Fan From: srikanth.4.yarlaga...@nokia.com [mailto:srikanth.4.yarlaga...@nokia.com] Sent: Wednesday, April 13, 2011 3:15 AM To: Zhao, Fan; meego-qa@lists.meego.com Subject: RE: A few clarifications around bug follow up Hello Fan The points specified by you are good and pretty clear. But, I have one more scenario to add up. Please let us know If there is a bug in 'New' state which was logged in the earlier releases, and in the latest release it is 'Not Reproducible' then what is your idea on this? Normally, we are adding the comment as 'Not Reproducible' and changing the status as 'Resolved Fixed', and we expect from the release to mark the bug as 'Release Fixed'. Br Srikanth Yarlagadda From: meego-qa-boun...@lists.meego.com [mailto:meego-qa-boun...@lists.meego.com] On Behalf Of ext Zhao, Fan Sent: 12. huhtikuuta 2011 16:53 To: meego-qa@lists.meego.com Subject: [Meego-qa] A few clarifications around bug follow up As I am observing some confusions about responsibility in bug follow up, I'd like to make some clarifications here. About bug RESOLUTION: Bug owners are encouraged to set bug status to "RESOLVED - FIXED" when they submit the fix to OBS, and to add a comment to specify commit ID. It will be much easier for release engineering team to track if the fix has been integrated. About bug REOPEN: Bugs cannot be REOPENED if they have been VERIFIED FIXED for more than 2 weeks. A new bug should be filed even though the behavior is the same or similar as the previous VERIFIED FIXED bug. The reason is that in most cases, the root cause would become different even though the behavior is similar, reopening old bugs will cause confusion. About bug verification: Bug reporter is responsible for verifying bugs following the "how to reproduce" instructions in the original bug report when the bug is marked as RELEASED - FIXED, and change bug status to VERIFIED if the bug is not reproducible; If bug reporter doesn't come back to verify bugs in 2 weeks after bugs have been marked RELEASED - FIXED, QA contact will help to retest and verify the bugs. If QA contact has difficulty to follow up the original bug report, and fails to get clarification from reporter, QA contact will set the bugs to "CLOSED" status in one month after the bugs are set to RELEASED-FIXED. Feel free to reply this email if you have questions or different opinions. Thanks, Fan
_______________________________________________ MeeGo-qa mailing list MeeGo-qa@lists.meego.com http://lists.meego.com/listinfo/meego-qa
