Decide on a version support policy

[mjtamlyn]

There is at least once benchmark which checks for compatibility before Django 1.2... It is nice to keep this is as long as possible but with changes to migrations/syncdb, app loading and the startup process it is becoming harder.

I'm not averse to supporting say, all Django >= 1.0, but I feel perhaps 1.4 would be more reasonable at this point.

[akaariai]

1.4 would be nice to have. I don't care about earlier versions.

EDIT: sorry for closing, I had a sudden stroke ofclumsy fingers syndrome.

[mjtamlyn]

As of b52fccf the benchmarks all run back to 1.4. There is at least one failing benchmark for 1.3 due to the addition of the url() function.

If we decide we are happy to drop support for <1.4, we can remove some older compatibility code:

• the query_exists benchmark is special cased to not run before Django 1.2
• The template_render benchmark has special paths for Django 1.3 where url reversing in templates was still done by literal rather than by string.

Either way we should document our decisions.