Hi,
The meeting minutes:
http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-06-21-12.00.html
Meeting summary
---------------
* Current status (E-P, 12:01:27)
* illustrated doing a tsestable image in 30 mins and booting it on
raspberry pi (Stskeeps, 12:02:51)
* in 30 mins (Stskeeps, 12:02:54)
* worked perfectly (Stskeeps, 12:03:00)
* testrunner-ui needs to go onto mer:tools (Stskeeps, 12:03:11)
* used eat, testrunner (Stskeeps, 12:03:11)
* OBS copyproject verified working (important for the automated image
creation) (lbt, 12:05:49)
* kernel command line can be used for bringing up eth0 on boot, and
this can be done in .ks file (E-P, 12:12:00)
* OBS upstream is using travis-ci.org to do CI on their github tree
for master branch; This could be useful for MerOBS too. (lbt,
12:13:33)
* Acceptance criteria for the tools and tests (E-P, 12:18:24)
* gerrit might cause some problems due to per-commit nature (E-P,
13:09:12)
* code review, integration and testing are required for tools (E-P,
13:09:18)
* each tool must have a wiki page with url to the right version
control (E-P, 13:09:22)
* using submit requests for tools with link to the changes diff (E-P,
13:09:25)
* submit requests are done from Mer:Tools:Testing to Mer:Tools (E-P,
13:09:32)
* Tools team updates the tools to Mer:Tools:Testing (E-P, 13:09:37)
* Mer:Tools:Testing is used for wider testing before SR are accepted
(E-P, 13:09:48)
* Mer:Tools is always ready for release (E-P, 13:09:56)
* using the same process for Project:MINT tools (E-P, 13:10:04)
* only accepting tests that are passing, failing tests are rejected
(E-P, 13:10:24)
* otherwise using the same process for tests that for the tools (E-P,
13:10:37)
* the test should pass on all devices, for now we can use virtual
machine (E-P, 13:10:48)
* Packages that are shared between MINT and Tools should be 'mastered'
in Tools (lbt, 13:11:21)
Meeting ended at 13:14:30 UTC.
-E-P
On Wed, Jun 20, 2012 at 11:39 AM, Esa-Pekka Miettinen
<[email protected]> wrote:
> Hi,
>
> I am back from my vacation, so let's have the next Mer QA meeting on
> Thursday 21th of June 2012 at 12 UTC in #mer-meeting.
>
> Agenda for the meeting is following:
>
> 1. Current status
> * The last meeting minutes:
> http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-06-14-12.01.html
>
> 2. Acceptance criteria for the tools and tests
> * http://wiki.merproject.org/wiki/Quality/Development
> * Code review
> * Unit tests for tools
> * Test cases tested on the HW or virtual machine
> * Only accepting passed test cases or should we also accept test cases
> for future features, meaning that test cases are failing until the
> feature is done
> * Maintainers for the tools and tests?
>
> If you would like to add anything to the agenda please let me know.
>
> -E-P
> Mer QA Technical Lead
