Release v0.10.7
Clarify report or throw error comment.

The issue of this comment not being clear enough was brought
up in a Gecko bug: https://bugzilla.mozilla.org/882677
Pull text-encoding from npm instead of a git submodule.

Note: the stringencoding lib has now changed names to text-encoding.
See the work going on at https://github.com/inexorabletash/text-encoding
to port this to npm and bower.
Release v0.11.0
Build the dist when we release a new version.

I've created a new Grunt task to build the distributable for
bower and bump the versions for npm and bower.
Release v0.11.1
Update npm dependencies to latest.
Use offical version of json-stable-stringify.

My PR to add the functionality that we need to this lib
has landed in the offical repo, so we should use that.
Release v0.11.2
Re-enable 'unused' config option for jshint.

This was supposed to have been done a long time ago, but got
forgotten about. Most of the issues have been cleared up since
then. Just one small issue remained which I've fixed in the
BoxPosition class.
Don't build lib/stringencoding into the dist.

This file doesn't exist anymore since we moved to getting
text-encoding from npm instead.
Don't ignore bower_components since we don't have any.
Don't build the dist files unless we explicitly want to.

In the normal course of development we should instead rely on a dev
build of vtt.js. This minimizes the possibility of accidentally
building and commiting an official dist while developing.

I've also updated cue2json.js to use the dev build instead of node-vtt's
default page, which will be running an older version of vtt.js.
Add develop vtt.js portion of README.