#meego-meeting: MeeGo QA Weekly Meeting 20110705

Meeting summary

1. Opening and general news (FanZhao, 06:57:52)
   1. 1.3 release schedule is published @ http://wiki.meego.com/Release_Engineering/Plans/1.3 (FanZhao, 06:58:40)
   2. MeeGo bugzilla instance code has been released on gitorious https://gitorious.org/meego-bugzilla. (FanZhao, 07:09:34)
   3. ACTION: iekku to take need-triage bugs to the core bug triage (iekku, 07:19:37)
   
   
2. Actions from previous meetings (2011-06-28) (FanZhao, 07:20:21)
   1. ACTION: iekku to send info mail to meego-qa and meego-handset list about our plan to close not maintained handset UX bugs (FanZhao, 07:21:47)
   2. specific for QA contact, the R&R is defined @ http://wiki.meego.com/quality#Questions_and_Answers (FanZhao, 07:28:06)
   3. ACTION: ericlr to create a proposal under the QA page to define the R&R for bugzilla lead, EM etc. FanZhao could help and lead the conversation after ericlr's ap is done (FanZhao, 07:37:40)
   
   
3. Update to QA status (QA Leads and QA-tools) (FanZhao, 07:38:38)
   1. netbook status is available in wiki now: http://wiki.meego.com/Quality/Meetings/QA_leads_update_1.2#Netbook_Update (FanZhao, 07:39:39)
   2. tablet status is available in: http://wiki.meego.com/Quality/Meetings/QA_leads_update_1.2#Tablet_Update (FanZhao, 07:42:31)
   3. http://wiki.meego.com/ARM/N900#Release_schedule (srikanth_rst, 07:46:16)
   4. for handset, we had 2nd summer release for N900CE, performance is better than SF release (FanZhao, 07:46:47)
   5. IVI: we are still working on first update for 1.2.0: 18 bugs have been fixed, 7 approved update blockers are open. See detailed bug fixing status at http://wiki.meego.com/Quality/IVI_1.2_Update. (FanZhao, 07:47:59)
   6. First testing repo is ready at http://repo.meego.com/MeeGo/builds/1.2.0/1.2.0.0.1.20110629.1/, but verification is blocked because package rpm version on the update repo is lower than 1.2.0 final build.  We workaround it by pulling packages manually to verify bug fixes. Several critical crashes issues have been fixed, and the quality improves a lot. (FanZhao, 07:48:32)
   7. SDK: we have continued the bug verification process and we have finished the VMM test cases. we have an working harness for Qt Mobility API testing for MAC OS and Windows OS (FanZhao, 07:51:39)
   8. SDK: or the basic and sanity tests we have started using TestKit on other OS than Fedora 13 we have a few issues which should be fixed soon. (FanZhao, 07:54:23)
   9. core status is updated @ http://wiki.meego.com/Quality/Meetings/QA_leads_update_1.2#Core_Update (FanZhao, 07:55:27)

Action items

1. iekku to take need-triage bugs to the core bug triage
2. iekku to send info mail to meego-qa and meego-handset list about our plan to close not maintained handset UX bugs
3. ericlr to create a proposal under the QA page to define the R&R for bugzilla lead, EM etc. FanZhao could help and lead the conversation after ericlr's ap is done

Action items, by person

1. ericlr
   1. ericlr to create a proposal under the QA page to define the R&R for bugzilla lead, EM etc. FanZhao could help and lead the conversation after ericlr's ap is done
2. FanZhao
   1. ericlr to create a proposal under the QA page to define the R&R for bugzilla lead, EM etc. FanZhao could help and lead the conversation after ericlr's ap is done
3. iekku
   1. iekku to take need-triage bugs to the core bug triage
   2. iekku to send info mail to meego-qa and meego-handset list about our plan to close not maintained handset UX bugs

People present (lines said)

1. FanZhao (114)
2. iekku (37)
3. IonutGavaz (20)
4. ericlr (18)
5. srikanth_rst (11)
6. Stskeeps (8)
7. dtao (8)
8. yanshuang (6)
9. MeeGoMeetBot (2)
10. timakima (1)