#JSX => #jsx
Add bitwise lint escape to DefaultDOMPropertyConfig
Ensure attribute values are strings

`jsdom` behavers differently than browsers here and we should ensure
that we are consistent. Browsers should be (and are) converting to
a string first, while `jsdom` doesn't.
Standardize prop -> DOM attribute process

Allow more than strings and numbers to be used as attributes for DOM
nodes. This removes the special casing for `0` and `false` that was
being used in ReactDOMInput and ReactDOMTextarea.

Now we will just `toString` any object we try to insert into a DOM.

Closes #422, #372, #302
Be consistent with object naming in tests

This also fixes line length issues our linter was complaining about.
Make sure DOM components work in JSDOM
Merge branch 'SanderSpies-sspi-dom-attribute-process'
Merge pull request #426 from SanderSpies/sspi-fix-jsx-doc-link

In-browser JSX warning linked to wrong anchor (should be lowercase)
new addons docs

closes #403
Updated AUTHORS for 0.5

closes #414
Fix Lint

Enabling bitwise linting caught another user. Also fixed a semicolon
misuse.
Use getActiveElement module

We had something that did the same sort of protection. The module
differs slightly (returns document.body instead of undefined) but
looking at the callers, that should be ok.
Enable linting for bitwise operators
Update docs with supported tags and attributes
bump baseline jstransform and esprima dependency versions
Update browserify
bump version to 0.6.0-alpha
Fix `grunt npm:test`
0.5.0 release

Updated README, CHANGELOG, blog post
Fix live editor examples on home page.

Remember that one time I wrote release notes and said:

> This is a breaking change - if you were using class, you must change
> this to className or your components will be visually broken.

Good thing I didn't listen to myself!