The MeeGo SDK QA Team is responsible of MeeGo platform SDK Quality. QA members focus on different components, host and target platforms, but we maintain all the test cases in the same testlink website, file bugs to MeeGo bugzilla SDK project, post testing report to MeeGo quality WiKi page. The synchronization among QA members is ensured by weekly SDK QA meeting, IRC and mail.
The default assignee of a newly introduced bug must set the bug to ASSIGNED in 1 business day if she/he is not on leave. In case he is not the one to solve the bug, he must pass the bug to another person leaving the status unchanged in 1 business day if she/he is not on leave.
Developer needs to set bug to ASSIGNED even if he won't start working at the bug right away. The ASSIGNED state is just an indication that the bug has reached the person/persons that should take care and fix it; bugs should have a short life in the NEW state. In case a bug remains in NEW state for longer than 1 week, QA must take action to search and notice the right persons; maybe the bug was misplaced? The recommended way of asking for describing anything that is related with the bug is by commenting in bugzilla rather than email or chat; this way other people can see all information related to the problem in one place
One unwanted situation is when bugs are in NEW and nobody has ever commented on it for a long time. Feedback is important to the QA, even for INVALID or DUPLICATE bugs in order to improve the QA process for the future and to help any other viewer that might run into the same bug later. Another situation to be avoided is when developer works on fixing bugs based on his own preferences, for instance avoid writing for bugs for documentation. This will contribute to an overall reduced quality process.
Once the release is about to take place the QA should release an acceptance document enlisting the last versions of the builds tested, overall status of the product (GREEN/YELLOW/RED) and some of the major bugs. RED should mean that the build is not ready for release from QA POV.
You can find uniform MeeGo SDK test plan @ SDK Test Plan