id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	size
25	Investigate South's resilience to failed migrations	geofft		"We've seen that it's possible for South to silently ignore some migrations and carry on to future migrations (in particular see r31e4eaa4e417aa48ec6bcff79f4e792abf7a7763). We don't currently understand in perfect detail how South searches for valid migration files, and stores its current state.

It would be nice to ensure that if someone botches a migration, or if South changes in some backwards-incompatible way, manage.py won't attempt migrations out of order (because on our current database server, South goes ""sorry, would you like to drop the DB and try again?"", which isn't particularly practical)."	task	new	normal	Sometime	Infrastructure					medium