The next step after bug 1320136. Once enough time has passed for all environments (including Vagrant instances of contributors) to be up to date with the squashed migration, the old migrations files can be deleted. (Doing so too soon will mean people will get errors when running migrate and would have to drop-recreate the DB.) I'd imagine we'd want to wait at least a few weeks. In addition to deleting the old migration files, we'll need to: * Updae all migrations that depend on the deleted migrations to make them depend on the squashed migrations instead. * Remove the `replaces` attribute in the Migration class of the squashed migrations (this is how Django tells that it is a squashed migration).

Comment on attachment 8841516 [details] [treeherder] mozilla:rm-squashed-migrations > mozilla:master Great stuff, thanks!

Commits pushed to master at https://github.com/mozilla/treeherder https://github.com/mozilla/treeherder/commit/c860a8035b2d212050e378b82d360e908b5d7564 Bug 1334329 - Remove migrations made redundant by migration squashing It's now been a month since the squashed migrations landed. This cleans up the old unsquashed migrations following the steps here: https://docs.djangoproject.com/en/1.10/topics/migrations/#squashing-migrations If anyone hasn't run migrate locally since, they can either: 1) Update to the parent of this commit and do so first 2) Destroy their vagrant instance and provision from scratch https://github.com/mozilla/treeherder/commit/f91611f6464b877a4bc8dbb39780b786e810c5df Bug 1334329 - Stop ignoring linter errors in migration files Now that we're on Django 1.10 (which doesn't add unused imports) and the old migrations have been removed we no longer need to ignore them and risk hiding real breakage.