I'd also recommend against splitting your models into a separate repo. There's a decent article on migrations without downtime here: http://pankrat.github.io/2015/django-migrations-without-downtimes/
Essentially "don't run your migrations at the same time as you deploy" and "split deployment/migration process into multiple steps, so you don't ever need to be in maintenance mode". Doing this is more work, so weigh those costs against your costs from being in maintenance mode for a few seconds every now and then, and figure out which is more important from a business point of view. For your other consideration of "smaller releases" I'd strongly recommend feature flags. Together with a well-tested codebase they'll make it far easier to get to continuous integration and release. Small, frequent releases also require good monitoring. I'd recommend taking a look at opbeat on that front. Cheers, Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/80cfacb0-5282-4148-8b5e-f69768639c22%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
