Add callbacks to a queue and schedule a task to flush the queue instead of scheduling an async task for every callback, .

Previously, we were using setImmediate when it exists. However, due to #115,
we would like to stay away from it for IE 10 and we don't really need it for
node since this new approach does not result in deeply nested `nextTick`s.
(See #66 for background on the node issue.) It turns out that these are the
only two supported environments that setImmediate is implemented.

Fix npm integration

version bump

fixing tests for rethrow in IE 6,7,8 as well as phantom/node

Rsvp#rethrow

Rethrow makes sure that any exception in your promise chain won't
swallowed:

getJSON('/posts.json')
    .then(handlePost)
    .fail(RSVP.rethrow)

You can also to chain it further, like so:

getJSON('/posts.json')
    .then(handlePost)
    .fail(RSVP.rethrow)
    .then(null, handleRejection)

adding promise#fail

- toString.call([]) angers IE, use Object.prototype.toString instead
- getPrototypeOf polyfil

toString.call([]) fails while the Object.prototype.toString.call([]) works

upload passing builds to s3

async: use three args for addEventListener

The third argument for `addEventListener` and `removeEventListener`
is supposed to be optional, defaulting to `false`, but some browsers
(notably older versions of FireFox) require it.

See https://github.com/thinkpixellab/PxLoader/issues/5 and
https://developer.mozilla.org/en-US/docs/Web/API/EventTarget.removeEventListener

some a+ 1.1 spec fixes.

with a `TypeError' as the reason.

Fix callback assimilation

Run reduce tests only in node

Add multiple resolve test

This was handled for some code paths but not all.

Removed the double try/catch

This allows the VM to optimize correctly.