Hi, Thanks for all participants. Here are the meeting minutes from the meeting. I am sorry for the delay.
-E-P ====================================== #mer-meeting: Mer QA meeting 12/4/2012 ====================================== Meeting started by E-P at 12:01:21 UTC. The full logs are available at http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-04-12-12.01.log.html . Meeting summary --------------- * LINK: http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-04-12-12.01.log.txt to catch up, for those late joining (Stskeeps, 12:05:19) * QA Process (E-P, 12:05:38) * LINK: http://wiki.merproject.org/wiki/Quality/Terminology helps at least (Stskeeps, 12:15:57) * LINK: http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-04-12-12.01.log.txt to catch up, for those late joining , mdfe (Stskeeps, 12:16:09) * LINK: http://wiki.merproject.org/wiki/Architecture (Stskeeps, 12:19:28) * LINK: http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-04-12-12.01.log.txt to catch up, notmart (Stskeeps, 12:29:39) * Mer Core would have change and release testing (E-P, 12:40:41) * Change testing is lighter than release testing (E-P, 12:41:24) * Release testing contains test for changed packages + Core test set (E-P, 12:41:52) * The test:package mapping needs more sophistication than <pkgname>-tests:<pkgname> (lbt, 12:44:14) * Tools and tests (E-P, 12:47:40) * tests should ideally be run at a discrete point in the process, not just/always inside the build environment (lbt, 13:00:28) * tests should be easy to execute, eg using zypper to install them and then just 'executing' (E-P, 13:01:14) * QA tools should go into Mer:Tools (E-P, 13:02:27) * QA tests should go into Mer:QA (E-P, 13:02:39) * work on bringing 'eat' up to mer/systemd ability (Stskeeps, 13:04:08) * innovative ideas welcome on how to extract tests made during the build process, to be run later on actual hardware (lbt, 13:04:50) * ACTION: Create git and OBS projects for QA tools and tests (E-P, 13:05:28) * goal for nextg week: we make it possible to add testability enabled images we can actually run simple tests against (Stskeeps, 13:06:53) * ACTION: E-P to document a little about how the CI testing was done in Maemo (lbt, 13:09:21) * OBS Publish process should distribute test packages to the right repos (cf -cross) (lbt, 13:10:12) Meeting ended at 13:11:34 UTC. Action Items ------------ * Create git and OBS projects for QA tools and tests * E-P to document a little about how the CI testing was done in Maemo Action Items, by person ----------------------- * E-P * E-P to document a little about how the CI testing was done in Maemo * **UNASSIGNED** * Create git and OBS projects for QA tools and tests People Present (lines said) --------------------------- * Stskeeps (82) * lbt (67) * E-P (59) * mdfe_ (15) * timoph (11) * iekku (4) * Kaadlajk (3) * MerBot (2) * Sage (1) * vgrade (1) * notmart (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.merproject.org/wiki/Meetings
