Initial plans

[Stelian Ionescu]

Hello,

Thank you for your interest and for joining this list.

I've forked the 3 repositories that we will have to contribute to. We'll work on the branches collaboratively, then when we think we're ready we'll send a pull request to TravisCI. This way we have all changes in one fork and we don't develop from our private forks.
Luis and Masatoshi have already been added to the team, all the others please send me your Github usernames so I can invite you to the team.

Let's keep the relevant discussion on this mailing list or on TravisCI pull requests so that everybody is aware of issues: e.g. if you have an idea and tweet about it please also send an email to this list or open an issue as feature request.

Here's my initial development plan:

We can start with re-implementing the exact functionality of cl-travis:
 * for each implementation, only use a hard-coded version
 * use CIM as command-line wrapper
 * install Quicklisp

We'll need to work on the travis-build project and create
 * lib/travis/build/script/lisp.rb
 * spec/build/script/lisp_spec.rb
then add an include in lib/travis/build/script.rb

According to the documentation in http://docs.travis-ci.com/user/languages/community-supported-languages/, the build process has 5 phases:
 * configure: here we must do all system changes like installing packages with apt-get. After this phase sudo will be disabled in container-based builds
 * setup: install the lisp implementations, the implementation manager and Quicklisp
 * announce: print some useful message about what just happened, like the lisp-implementation-name and lisp-implementation-version
 * install: nothing for us here. This phase is just for the individual project to install more stuff
 * script: the main phase. We could add a default implementation that quickloads the test ASDF system and runs the test suite, assuming some common naming scheme for the packages

Once we have this done, we can think about implementing the more advanced features of TravisCI like a build matrix, UI changes, or supporting more versions for each implementations, etc... I'll setup a wiki too so that we document the current features.

Thank you again.

-- 
Stelian Ionescu a.k.a. fe[nl]ix
Quidquid latine dictum sit, altum videtur.
http://common-lisp.net/project/iolib