> What are 'all the elligible files'? All (only) the sample files that > should be in the release?
Yes, only the sample files with their libs. For instance, now.jal is not a lib, associated sample can't be released, so they're not elligible. Sounds ok ? > > > Remove it from the file. Replaced ? Change the appropriate line. > > Changed? You don't mean each revision number, do you? No !... Changed == renamed > > > As the wiki page we first had, this file could have 2 sections: libraries > > and samples. Samples are sufficient, though: if a sample is elligible to > > a release, by "simply" analyzing include statements, I can select the > > correct libraries to be included in the release, too. This is also a way > > to force us to supply at least one sample with a library. > > Sounds okay. There are quite a few blink examples though. Won't a list > of files in sample/by device do? Sorry, can't understand what you mean about "few blink examples" > What is the added value? f we know the SVN revision of a release, we > can check this version if we want to investigate a problem which can't > be duplicated with the head revision... That's right, but if people takes file from the repos, through the web interface, there's no way to know which one they take. At least, without doing archeologic work... This is also a way to know the revision, without having to use svn executable (or a svn library, like in my jallib.py script). > I do like the general idea. I think we can estimate the risk of any > change pretty well and test accordingly. The risk of introducing a > large number of bugs in code that used to work before is limited. > So we can work on the content, release often and as little as possible > effort in the 'software process'. Yes, this is a "worked before so should still work" approach. Sounds appropriate since we're all very serious :) 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 -~----------~----~----~----~------~----~------~--~---
