I've just tried it with 1.7 and several things pop up quickly.
The dashboard page is broken. This must be due to some html changes introduced in 1.7. Also, we must support index_title site_header and site_title that were introduced in AdminSite
There's also the new migration system. We can support both south and contrib.migrations if we wish so by using south_modules and migration_modules [2, 3]
And finally the new app loading refactor. Apps now have a verbose_name to be used in the admin.
How would you like to tackle all this?
- A backwards incompatible release; since there's quite a few changes it might be a good idea, and leave a maintenance branch for bugfixes
- Support several release in only one branch
- Support 1.7 in a new branch and maintain another branch for older releases.
I would personally go with option 1 or 2, but in case we decide option 2 we might think about deprecating a couple of django versions, supporting django from 1.5 o 1.6.
 https://docs.djangoproject.com/en/dev/releases/1.7/#django-contrib-admin  https://groups.google.com/d/topic/django-developers/ekZptI00toU/discussion  http://treyhunner.com/2014/03/migrating-to-django-1-dot-7/