reset migrations
jamesturk opened this issue · comments
a few of the migrations created are pretty bad/pointless but there is a bug preventing squashing them in Django right now.
since nobody is depending on this yet, prior to a 'real' release we should reset the migrations, preferably when Django 1.7 comes out.
since things are still in flux as a result of the OCDEP process this can wait until 1.0 (or whatever release comes right before it)