title: Django squash or eliminate migrations on production
body: <p>I have an app on production. It has 251 migrations that take too much time when I run the tests, it is making development really slow. I need to do something about this and I'd like an advice. Is it recommendable to squash the 251 migrations? what if I erase then and then just <code>fake initial</code>? of course, I can't lose or change the database, it is on production. Thanks a lot for your help.</p>