Hi Joris,
Your observation is absolutely right, the master branch always try to catch up with the clang trunk updates.
We have release branches that are ensured to work against a stable version clang, for example, oclint 0.7 branch will work for clang 3.3 release.
We can't release 0.8 version based on clang trunk, but current clang trunk will be branched out by the beginning of Dec, at that time, we will branch our code for oclint 0.8 version as well.
I personally prefer running against clang trunk for oclint master branch, this will help reduce the technical debt of this project, which helps in a long term. Another benefit of employing a continuous integration is that, we actually don't need to update clang everyday on our development box unless the build turns red, since CI will always build a fresh clang for us, and guarantee us a broken build when Clang changes its API.
Thanks,
Longyi