Hi Seb, This is a great idea! Real continues integration requires automated regressions tests and that is probably a bridge to far. But in most cases of jallib, we can be pretty sure that a change in a lib is okay when it is tested on one relevant PIC and it compiles with all relevant tests and samples.
Joep 2008/10/25, Sebastien LELONG <[EMAIL PROTECTED]>: > > > Talking about programmer's discipline.... > > Discipline... I'm gonna set up a buildbot for jallib, so it can check how > disciplined we are here :) Something like CruiseControl, and a simpler one, > python-based, everyone could install. This would really help us to avoid this > kind of surprises, and catch them at the very moment they appear. > > * http://en.wikipedia.org/wiki/Continuous_integration > * http://en.wikipedia.org/wiki/CruiseControl > > Once set, you can't imagine how helpful it is. And yes, jallib deserves this > kind of tools, as it deserves a version control system like subversion. > > > > Since Eur seems not with us now, I'll make the hello_world_lcd sample. I > > can probably also test it. > > OK. But don't hurry, we can do this later or postpone the beta. > > I'm off now, until this evening or tomorrow. > > 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 -~----------~----~----~----~------~----~------~--~---
