Hi Albert, , > Saw that you commented out the test option in jallib, it might be wise > to update the wiki page.
You're right, I'll do this ! > For my information, what is the new procedure > for updating the test matrix? There's no procedure, because there's no test matrix anymore (ever, that was just a prototype). The process now is: - write your lib - write a sample - both must JSG compliant (Jallib Style Guide) - if no flaming discussion appears on the list, and if you're confident and satisfied, put your lib + sample in TORELEASE file (/trunk/TORELEASE), so it's included in next release You have some of this sum up here: http://code.google.com/p/jallib/wiki/ValidationProcess We used to debate a lot about how to test, what would be the procedure, how to register test results, what about regression tests, etc... We finally conclude it would be more pragmatic to test as much as we *can*, and spend time in documentation, tutorial, howto, advertise (for instance, jallib blog). We also count on user's feedback to fix what needs to be fixed (as it already occured, and this seems to work quite nice). I can see two critical points IMHO when performing tests: compiler and device files. When compiler is changing, I would say we need test everything. When device files are changing, well, it depends on Master Rob's decision, he tells us how confident he's about new device files' version. Of course, all of this is not written in stone, and suggestions, remarks, etc... are truly welcome. Cheers, Seb -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
