 |
lua-l archive |
|
|
||
|
On Mar 10, 2013, at 7:21, "Peter Drahoš" <drahosp@gmail.com> wrote:
If the CI is already in place, and all that is needed is some licenses, then I will see what I can do. I suspect that a 64bit win 7 and 32bit XP license will not be a problem. If we were doing this at my work, I'd guess that we'd use our MSDN licenses to do this. Having someone else do it is more than worth the cost of licenses, however.
I'm not sure how someone provides a Mac OSX vm, without a Mac OSX. If that's doable, let me know. Otherwise, I might be able to get creative with something, but then I have to ask if the person has room for an older iMac? Not sure if I can do that, however.
We are in the process of setting up Jenkins (I believe). It's not that I have an opinion about it, it's only that it may be possible for me to help in that way, if it turns out that a CI machine is not available.
As far as standards go: I think recommended guidelines are great. I think CI assert-able testing is what will most likely change things. Asserting things like: It installs on key platforms.
It can be 'required' in 5.2 and 5.1 without error. (This means dealing with the sticky detail of installing foreign libraries, or a method to mock them) It has a test directory, with tests made in such a way that the CI server can run them and detect the results.
It passes those tests. It has a /doc/index.html file that isn't 0 bytes and can be opened by a viewer, without error. It uses the included build system. Hopefully I'm not repeating someone that I missed...
-Andrew
|