I also suggested that they improve the production deployment situation somehow. I spent two days the first time I deployed a Django app to production, between installing supervisor, gunicorn, nginx, mysql, etc and debugging all the issues. (Mostly getting paths right, and having the wrong .'s in imports.)
Django could release and update with every release.
I'm hoping it won't be too hard to add a deployment story at the end.
Deployment is a pain. Perhaps some official tutorials would be good in the interim.
https://github.com/GrahamDumpleton/mod_wsgi-docker
I've been evaluating using uwsgi as a stand-alone server. I'm not sure how much load it would support, but I think it's possible get quite far with Django, sqlite, and uwsgi.
Thinking about it a bit more, there could be less directory settings in Django itself. Maybe there could be more "convention over configuration" outside Django too. I do remember it being a pain doing it first time since you don't know where all the log files are.
(don't mind the stale release, just use master)
It is a much, much better admin-like tool to use for building CRUD views, with strong conventions on permissions, URL structures and template names. It really simplifies things and we've been using it internally for four years on a dozen different projects.
Can't imagine using Django without it.