I didn't mean to imply jumping from 1.4 - 1.8 and then fixing all the issues would be the best way forward. I was thinking along the lines of a one page common upgrade issues that summarised the back-compat changes from the previous releases, separated under each release header.
Anyways, this is slightly off-topic (sorry), I'll move this discussion to a new topic or discuss in IRC. On Saturday, 18 October 2014 10:14:14 UTC+11, Tim Graham wrote: > > If you are upgrading from 1.4, I would recommend going step by step > through each intermediate Django version. I don't believe trying to upgrade > straight away to 1.8 would be easier. I'd encourage anyone on 1.4 to start > doing intermediate upgrades soon, so if there are still undetected > regressions from 1.4, we can start solving them now. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a6d245fe-45ea-44d9-bbf1-4c786f9166be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
