title: Naming conventions for Code First migrations
body: <p>We are using code first migrations to keep our database and model in sync. At the moment we have the version number as name for the migration which clearly doesn't work out. 
  The problem is that multiple migrations with the same name where created by different developers independent of each other for their local database. This led to some weird behavior as the <code>IMigrationMetadata.Id</code> was different because of the time stamp but the classes are partial with the same name.</p>
  
  <p>What is the way to go to call these migrations? The examples are always ridiculously oversimplified: e.g. adding a property <code>Readers</code> result in migration <code>AddReaders</code>. </p>
  
  <p>Or should the migrations be broken down to these little changes? Instead of having accumulate all the changes into one big migration. What if there are dependencies? </p>