===================================== #mer-meeting: Mer QA meeting 3/4/2012 ===================================== Meeting started by E-P at 11:00:36 UTC. The full logs are available at http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-04-03-11.00.log.html . Meeting summary --------------- * Current QA status (E-P, 11:05:09) * LINK: http://autodoc.meego.com/boss/processes/CE/MW/MTF/ (lbt, 11:22:17) * Mer Core has a CI system in place; each change to a core package is submitted for review before acceptance (E-P, 11:26:43) * Changed package is compiled to all architectures in OBS, and rejected if any of the build fails (E-P, 11:27:31) * BOSS is used to handle this process (E-P, 11:28:02) * Signaling system is not implemented and requires planning (E-P, 11:28:24) * automated image generation after each build and before acceptance is almost ready (lbt, 11:29:38) * QA Scope (E-P, 11:31:48) * 4 areas : SDK & Tools; Core; Hardware adaptations and other vendor issues; System (E-P, 11:49:37) * QA tools (E-P, 11:51:49) * Using QA tools from MeeGo, like testrunner-lite, OTS, test-definition, Testplanner, QA-Reports (E-P, 11:52:34) * Next in QA (E-P, 11:56:26) * LINK: http://wiki.merproject.org/wiki/Quality/ExecuteTests (E-P, 12:02:29) * http://wiki.merproject.org/wiki/Quality/ExecuteTests (E-P, 12:02:59) * ACTION: We need to define how the BOSS makes a test-plan (E-P, 12:12:07) * ACTION: Propose next meeting time (E-P, 12:13:23) Meeting ended at 12:14:06 UTC. Action Items ------------ * We need to define how the BOSS makes a test-plan * Propose next meeting time Action Items, by person ----------------------- * **UNASSIGNED** * We need to define how the BOSS makes a test-plan * Propose next meeting time People Present (lines said) --------------------------- * lbt (97) * E-P (85) * Stskeeps (8) * timoph (3) * MerBot (2) * iekku (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.merproject.org/wiki/Meetings