Bring the sample project into the repository
Tidy the model and remove dependency on mogenerator

It's a small project, don't want to put anybody off with unneeded dependencies
Add test targets for ARC and Non-ARC projects

Normally, I would just use one common test class, but I'll leave them as
individual ones for now to keep the tests more flexible.
Create test files that will actually be used

I prefer single test files, a public interface for a Unit Test doesn't make
sense.

Just a stub with an indication of the next test I will write.
Create a new version of the test apps model and write a failing test for migrations
Add support for Automatic Migrations
Update the Test Apps to use version2 of the model
Add a Readme to the repository
Add a .gitignore file

I'm so used to my system wide one, I forget to add them
to repositories, sometimes.
Only supply automatic migration options when configuring persistent store for reading
Makes no sense to migrate a store that's being created, right? I also like that this neatly solves the issue of overriding those settings should a subclass try to do so from *its* override of -configurePersistentStore…
Rename -enableAutomaticMigration as +requestsAutomaticMigration
Factor out internal +managedObjectContextClass method
Wrap async saves in -performActivitiy… call so previous saves finish up before proceeding
Use -performAsynchronousFileAccessUsingBlock:… instead of activity method

Was the wrong method to use; was deadlocking on quit, among other
potential problems
Avoid deadlock should subclass's additional content writing access the MOC/PSC
Run usual save routines after migrating a store
For some reason I had it in my head the migration include any pending in-memory changes! It really does just migrate the existing store though.
Remove -saveToURL:ofType:forSaveOperation:error: override
Looks like it was left over accidentally from original BSManagedDocument
Our -writeToURL:… routine should take care of any work it was performing
Clarify how additional content is handled during sync writes
Use autorelease pool during reverts
Allows UI to be torn down a little more immediately
Revert using parent context's private queue when available
Otherwise, reverts tend to deadlock