chore: update contributors
chore: release v0.11.3
docs(installation): use karma-cli
style(browser): correct spelling of the warning
fix(browser): reply "start" event

When a browser creates another socket.io connection, we forget the old one, however we need to reply all the events that happens in that connection. Somehow I forgot to reply "start" event, which caused the "Adapter did not report number of tests" warning.
style: make jshint happy
chore: release v0.11.4
feat(launcher): send SIGKILL if SIGINT does not kill the browser

In some cases chrome on linux does not die when it receives a SIGINT
signal. So after a SIGINT is sent, wait 2 more seconds and issue
a SIGKILL if the process is still running.
docs(config): clarify file expression examples
test(e2e.requirejs): show how to use relative dependencies
fix: do not execute already executing browsers

This was causing iframe reloads on IE8/IE9. These browsers use xhr-polling and socket.io does re-connects pretty often. We need to start execution only when the browser connects for the first time, no other re-connects.
chore: update contributors
chore: release v0.11.5
docs(intro): fix a typo

Closes #839
feat(browser): improve logging
fix(config): apply CLI logger options as soon as we can

We use logging even before parsing the config file - for instance to show the path of the config file that is actually being loaded. At that time, we can't configure the logger based on the config file, but we can already apply the command line arguments.
fix(config): ignore empty string patterns

An empty string pattern is a mistake - there is no reason to do that. It can however happen (for instance when you generate the config file).

Before this fix, Karma would try to watch this empty string pattern, which would result in watching the entire `basePath` directory.

Now, the pattern will be ignored and a warning showed.
test(e2e): add a test for coverage of coffee script files
docs(intro): fix formatting
feat(client): show error if no adapter is included

Before this fix, Karma would just execute "an empty" test suite. The next run would however end up with an exception (Property "start" is not a function).

This should make it easier to understand.