WIP on embedded records
added callChangeEvents
relationships now indexed based on parent, child, parentKey, childKey
made keys for relationship changes be childKey+parentKey
changed relationship to be simple two sided, only 9 failing tests
removal from old manyArray when added to a new one works
added relationship pairs function and made coalescing work
deleting old code
deleting more old code
Clear relationships before dematerializing

The relationship change object needs to look up the record type in the
store (so it can find and unset inverse associations). Dematerialization
needs to occur after that happens, as it removes it from the store's type
lookup table.
Start writing tests for the new API
refactor oneToManyChange into RelationhipChangeAdd and RelationshipChangeRmeove
Start adding pre materialization and extraction
When a problem comes along, you must WIP it

Start implementing Serializer#extract
Improved language in BREAKING_CHANGES
Even more improved language in BREAKING_CHANGES.md
rackup runs package=all by default
Merge pull request #520 from twinturbo/rackup-fix

rackup runs package=all by default
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' }
});
Merge pull request #490 from mhelabs/relationship_clear_on_delete

Clear relationships before dematerializing