Run CI against Node v0.11 as an allowed failure

[jugglinmike]

Building against the latest unstable release of Node.js should help the
project stay on top of any bugs or breaking changes to the platform.
Specifying that build as an allowed failure guarantees that unforeseen
errors do not block ongoing work.

[matthewmueller]

@jugglinmike interesting, so what does this show? Green light on a PR, but failed in Travis?

[jugglinmike]

@matthewmueller Basically. It lets us know what's going on in the unstable version of Node by visiting the build page on TravisCI. This way, when 0.12 is released, we know what to expect.

Currently, the contextify library (a dependent of jsdom) is failing to build. There isn't anything we can do directly to resolve this in Cheerio, but it's still enough to block us from supporting Node 0.12 (whenever it is released). In this case, it looks like this is a known issue, but having this knowledge lets us be proactive in moving our dependencies forward.

[jugglinmike]

Typo in the commit message--updating..

[matthewmueller]

thanks man