Hi guys, While preparing the release, moving things from unvalidated to validared was a real p.i.t.a. Mostly because some files needed to be removed, added, renamed, etc... Kind of manual and conditional sync.
Anyway, I can remember someone saying "let's just forget about validated", and I think this would be a nice idea. Releasing shouldn't be a pain, it should be as easy as possible, mostly automated. The orignal matrix purpose was to store the tested files. The matrix could also be used to populate validated, and create a release. Now it seems too complicated, mostly because of "nasty" dependencies, which I can understand. Still, we have a problem: we can't release by simply "pushing the button". validated, while interesting in the beginning, is a kind of duplicate SVN branch, the one used for the beta. While there's a lot of work to maintain this validated map, most people, including us, don't care about it and prefer having a look at "unvalidated". This is also a duplication of information, regarding the matrix. Since the ETP (Eternal Testing Problem) is still there (well, it's eternal, isn't), and since we decided to "test as much as possible, without spending too much time, because building a user base is more important right now and if it doesn't work then people will report it, at least some will give feedback, and it's better spending some time advertizing jallib, amen", validated doesn't make sense anymore. But... not all files in unvalidated are elligible to a release. So we still need to store, somewhere, which files are supposed to be included in the next release. The matrix ! No, I'm joking :) I suggest the following: * add a "Revision: " field in JSG: it will store the SVN revision of the file. Don't worry, it's automatic, each time you commit a file, it's updated by SVN (see svn:keywords property for more) * maintain a simple file, where we can find all the elligible files. Format: a list of filename, full path. A new file should be added ? Put it this file. A file needs to be removed ? Remove it from the file. Replaced ? Change the appropriate line. 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. What about "Revision:" fields ? Well, extracting them, I can automatically populate the matrix, if we decide to. This is also a convenient way to know which is used, when reporting problems. Finally, using this file (which "just" matrix at a higher level), I can also write a script and a bot, to automatically create tarballs, and release once in a week, or every nights, or after the repository have been quiet for 1 week, etc... 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 -~----------~----~----~----~------~----~------~--~---
