Rename setup() method to _setup() on DS.Model
It is pretty common to find a DB column named 'setup'.
Previously I would do something like this to map around the problem.
App.Adapter.map('App.SomeModel', {
    // setup is reserved, so we have to map around it.
    _setup: { key: 'setup' }
});
Fix issues with parsing ISO 8601 dates in IE8
Include test to show error introduced with last embedded changes
AdapterPopulatedRecordArray triggers `didLoad` event at the end of the runLoooop

- Fixed reported integration tests
- Add Em.run to some tests which became invalid with this change
This allow to define integer ids in the fixtures, as well as integers

correct test title
Breaking changes.md update

- Added note about Adapter.configure for side loading
- Added a note about dirtying record changes
Make DS.RESTAdapter default adapter of DS.Store
Add a space in the assertion message
Demonstrate unwanted record sharing.

By adding a pingbacks relationship and not modifying it in any test, we
should end up with an empty array in all serialized Posts, i.e.

    {
        "post": {
            "comments": [
                {
                    "title": "Wouldn't a more lightweight...",
                    "user": null
                },
                {
                    "title": "This does not seem to reflect...",
                    "user": null
                }
            ],
            "pingbacks": [],
            "title": "A New MVC Framework in Under 100 Lines of Code"
        }
    }

However, what we get is

    {
        "post": {
            "comments": [
                {
                    "title": "Wouldn't a more lightweight...",
                    "user": null
                },
                {
                    "title": "This does not seem to reflect...",
                    "user": null
                }
            ],
            "pingbacks": [
                {
                    "title": "Wouldn't a more lightweight...",
                    "user": null
                },
                {
                    "title": "This does not seem to reflect...",
                    "user": null
                }
            ],
            "title": "A New MVC Framework in Under 100 Lines of Code"
        }
    }
Consider relationship for embedded hasMany records.

When serializing a relationship, the previous algorithm serialized all
records in _all_ has-many relationships, not just all records for the
specified relationship.
Only serialize has-manys that are embedded
Using FixtureAdapter, ids must be defined in the FIXTURES
improve error message
The owner record is now an argument passed to findMany on the adapter

While writing an adapter for my django backend I was unable to
build a valid url for my hasMany relationships because the owner
was not easily accessible. Going forward the owner will now be an
argument available for custom adapters like the one I ended up writing.

example of how my REST api would lookup hasMany relationships:

If I have a person with many occupations I would look them up like so

/people/1/occupations/

Notice the id 1 above is actually the owner of the occupations (not a
occupation id from the ids array that is passed into findMany)

Instead of passing each id like the built in RESTAdapter the url above
just expects the owner will know how to find each occupation
Fix active_model_serializer link

Repo was moved to rails-api organization
Fix typo in store error message
Extract embedded `belongsTo` records properly

`sideload` won't consider relationships/embedded records, by using
`extractRecordRepresentation` we'll recurse into the record (similarly
to `extractEmbeddedHasMany`).
Use of references instead of clientId
Trying to fix this using a new bucket