> > All by all I came to the conclusion it is not worth to take the risk to > replace the device files now. >
OK. > > But your idea seems good for regression tests. I'll give a try. > I don't understand. Validation of all device files together with > generation, validation and compilation of all blink-an-LED programs > takes a few minutes here. You'll understand I do this locally after a > checkout: no blocking of the repository at all. > You must do it significantly different.... how? > I do test the way you do. When I say "block the repository", I mean "feature freeze". By the time we decide to release, to create a validation page and fill it, to discuss, etc... there supposed to be only bug fixes, no feature added. Else, we eternally looping the process (add a new lib, validate it or not, discuss, add a new lib, etc...). We need to take a "snapshot" of the repos, and validate against it, then creating the release from it. About device files, the "problem" is everything depends on them. So if they're modified, it's like you warm the feature freeze up :) Validating beta01 shows we mostly vote for what we used *and* there's no negative votes. This means we, developers and responsible committers, could decide by our own to validate files or not. The approach this time was: let's discuss, then copy files. We could try the other: let's copy, we'll discuss later. Of course, this means that if there's a doubt about a file, you should not copy the file by our own. How to know if there's doubt ? If there're too much post on jallib groups :l Once libs are copied to "validated", we could run tests from unvalidated *against validated lib/devices*. Every sample/test which pass can be copied to validated, and this can be done automatically using the testing matrix. (and copying samples before libs is no sense for me). That's just some thoughts, for the next time... Another option is to create a branch and merge bugfixes to it (overkill IMHO). Seb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
