I upgraded from 1.3 to 1.5. That was the hard part I think. We are currently running version 1.10 and the updates to that version have been without a problem. That being said - it all depends on what your application does. If you do a lot of things that are specific for your application. The main problems I had was with changing to class based views for certain functions.
Also - you should really be upgrading to a supported LTS version regardless of what management thinks is necessary. The problem here isn't the time it takes to do the upgrade, but the things that are excluded by running an older version of django. Updates to django come on a regular basis and only come for the supported versions (right now 1.10 and 1.11). You REALLY don't want to run an old version of django because of security exploits. Regards, Andréas 2017-05-16 14:28 GMT+02:00 Mike Dewhirst <mi...@dewhirst.com.au>: > Go from 1.6 to 1.8.18 which is still supported and is easy. Buy some time. > Actually all the upgrades are easy. Well up to 1.10. I skipped 1.9 and > haven't tried to go to 1.11. > > Good luck > > *Connected by Motorola* > > > NoviceSortOf <dljonsson2...@gmail.com> wrote: > > > It's said here 1.11 is the recommended version of Django. > > Our upgrade from 1.1 to 1.6 took much more time that expected, > and management does not want to upgrade again. In terms of best practice > though I'd like to push for it. > > * Is an upgrade from 1.6 to 1.11 as complicated as migrating from 1.1 to > 1.6? > > Please advise > > -- > 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/89dfb079-65e5-4476-baf0-2ebfa286728b%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/89dfb079-65e5-4476-baf0-2ebfa286728b%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- > 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/o8hi5a20ukfnbnmaivhxhx3o.1494937708557%40email.android. > com > <https://groups.google.com/d/msgid/django-users/o8hi5a20ukfnbnmaivhxhx3o.1494937708557%40email.android.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAK4qSCe6MHRuvEe4_5cRZm9TSXfa6gCgcLwOAsoqjQy1ttHa5w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
