Adam, > so as a production side, I'd prefer to use test program rather than use > Flikernoise, or we must to use Flickernoise to test M1?
We will work out the exact rc3 production testing procedure later. Probably we will switch to a mix of testing in the test program, and testing in Flickernoise. We did a (very small) Flickernoise test already in rc2, by launching into it and testing USB keyboard and mouse in Flickernoise. You know how it is with testing - we have to be pragmatic above all. So yes, we should include some more Flickernoise actions in our test program, but not to replace the dedicated testing software, but to add to it. The dedicated test software can do tests that would not be possible in Flickernoise, and Flickernoise can give us confidence that we have tested what our users will do once they take the product out of the box... On RC3, Xiangfu will be the main person to provide all testing related documentation, binaries, etc. Of course Sebastien will help in the background as needed, if we run into difficult technical problems. That's the plan at least - what do you think? Wolfgang _______________________________________________ http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org IRC: #milkymist@Freenode Twitter: www.twitter.com/milkymistvj Ideas? http://milkymist.uservoice.com
