title: should south migration files be added to source control?
body: <p>I'm wondering whats the "best" way to use South with multiple developers.</p>
  
  <p>Should the migration files be tracked?
  The problems rise when two developers create different changes to models.py from a same origin.</p>
  
  <p>If the migration files are tracked:</p>
  
  <ol>
  <li>It is difficult to notice a merge is needed since they are formed with different file names. </li>
  <li>and it is difficult to merge anyway.</li>
  <li>difficult to apply (need to migrate backwards one migration, merge, migrate forward again)</li>
  </ol>
  
  <p>If they are not tracked:</p>
  
  <ol>
  <li>tweaking migrations can't be shared.</li>
  <li>a developer needs to <em>create</em> a migration (and apply it) whenever he pulls a change to models file (instead of just applying it). </li>
  </ol>
  
  <p>Are there more advantages/disadvantages I missed?  whats the "best" way?  I'm currently using tracked migrations but thinking of changing to untracked, seems its far simpler.</p>
  
  <p>thanks.</p>