Why not using travis (or another) ?

[Kerollmops]

Why not using travis to call cargo build, cargo test for each commit ?
Each pull request/commit can update the documentation...
I already use it on some of my rust libraries, so I can help you for that (I think) 😄

[c0gent]

Yes I need to set it up. Maybe I will do that this week. I'll let you know if I need any help.

[Kerollmops]

If you want, this document really helps !

[c0gent]

Excellent, thanks.

[pravic]

@Kerosene2000, it can be useful only for the docs. Because you cannot test OpenCL in arbitrary travis machine :)

[Kerollmops]

That's right ! I didn't think of that 😄
You can't ask a specific machine on travis ?

[pravic]

No idea, I've never tried the travis before.

[Kerollmops]

here is a little help file somehow, I don't really know if that works 🍋

[c0gent]

After some investigation, this won't be useful enough to warrant bothering with for now considering the constraints of an OpenCL environment.

Eventually a comprehensive, cross-platform test suite will need to be set up but I'm not sure that travis will necessarily be the way to do it.

Publishing documentation has been a simple shell script for quite some time and I see no reason to change that.