Fix Chronic tests by ensuring the hour and minute are set along with the
day on relative date tests.
Make relative date and time "15th at 8pm" work
Greatly simplify some logic.
Ensure parsing 'now' works.
Prep javascript tests to be run outside of a browser.
Add node-based test harness that uses nodeunit.
Add task to run tests.
Improving output.
Update README.
Annotate conditions in finish() in parser.js and remove unused
conditions
Provide a way to bias the dates parsed to either the past or the future

Biasing is signaled by setting the `bias` property to `past` or `future`
on an object that is passed as the second optional argument to
`Date.parse()`.
Make sure biasing works with "last week"
fix for ago / before functions of datejs
Timezones and Timezone offsets now parse correctly
- fixed timezone implementation for ISO8601 and RFC3339 formats
- added ability to parse milliseconds in accordance with ISO8601/RFC3339
- updated toISOString to output 3 digit milliseconds in accordance with RFC3339 format
- added specs for new functionality

Other changes
- removed build directory as newer frameworks typically contain asset pipelines and JS uglifiers
- removed outdated changelist as it is no longer required
- TODO updated
Merge pull request #2 from erikreedstrom/next

Timezones and Timezone offsets now parse correctly
Merge pull request #1 from ianso/next

fix for ago / before functions of datejs
Updated core formatter RegEx to handle foreign language articles
- "de", "ta", "gada", and "yil" are now supported
Added .gitignore
Updated parser so iso8601 formats without time parse correctly
- 2012-01-12 no longer parses as December 01, 2012
date.toString('d') does not return the right value in Chrome Canary.

Did not check other browsers, however getDate() should be safe across the board.