I strongly recommend this approach: My experience is that the best thing to do is to do minor upgrades - 1.8 -> 1.9.x -> 1.10.x -> 1.11.x (where x is the last patched version of each minor version).
Further, at the completion of one Django version, I recommend saving a snapshot of your database at that moment, and then starting the next upgrade in a new GIT branch : Git branches: mycode_django_1.8 # Working version under 1.8 mycode_django_1.9 # Working version under 1.9 mycode_django_1.10 # ... mycode_django_1.11 # ... On Monday, September 24, 2018 at 4:08:48 AM UTC-4, Andréas Kühne wrote: > > Hi, > > My experience is that the best thing to do is to do minor upgrades - 1.8 > -> 1.9.x -> 1.10.x -> 1.11.x (where x is the last patched version of each > minor version). The reason for updating in this fashion, is that when you > start the server on each version, you will get warnings about unsupported > changes in the upcoming releases. > > And of course - having a good test suite will be essential for upgrading > successfully. > > When you have done the django upgrade, I would then do the python upgrade > (just like others have suggested). Doing both at the same time will just > become a huge task.... > > And of course - like others have also stated - django 1.11 is the LTS > version, not 2.0. Upgrading to 2.0 is only necessary if you need the > features that 2.0 includes (which is mainly changing to a different > structure to the urls files and also deprecating python 2). > > Good luck! > > Regards, > > Andréas > > > Den sön 23 sep. 2018 kl 15:56 skrev 'David Brown' via Django users < > [email protected] <javascript:>>: > >> I have a large django project built in 1.8 with about 14 apps and a large >> amount of dependencies. >> >> I already have a good idea about how I'm going to update the 2.7 code to >> 3.6 or possibly just make it compatible with both, however, I'm not sure >> what is the best practice and most efficient way to refactor/upgrade the >> django framework to 2.0 from 1.8. >> >> Bare in mind this thousands of lines of code so efficiency in terms of >> work is crucial. >> >> Thanks in advance for all suggestions! >> >> -- >> 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 [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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/d6307d12-8920-434b-b5ec-e9b72c0c3443%40googlegroups.com >> . >> 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 [email protected]. To post to this group, send email to [email protected]. 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/4fe101e6-077f-4ce3-ac76-1f7a03100170%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
