Re: Migrating older 1.4 project to 1.9

I have also upgraded a few apps this way, from 1.5 to 1.9.  Keep your eyes on the release notes for each version for big changes.  It also helps to have good test cases written so that you can run them upon each upgrade.

---

From: "Gergely Polonkai" <gergely@polonkai.eu>
To: "Django users" <django-users@googlegroups.com>
Sent: Wednesday, March 30, 2016 1:06:45 PM
Subject: Re: Migrating older 1.4 project to 1.9

I have already suggested this approach to someone with a similar problem: upgrade one version at a time. I'm sure it is possible to find older versions; 1. upgrade to the next minor release (1.4 => 1.5, etc), 2. do the necessary adjustments, 3. goto 1.

It may be a lot of work, but at the end of the day you will have a perfectly upgraded application. I have successfully upgraded 3 apps this way, one of them being really big (tens of thousands of code lines).

Roger,

Yeah, I too have a large project that I'll hopefully be migrating
from 1.4 to 1.9 soon.

It's about 3.5 years worth of work, over 200,000 lines of code
in about 1000 Python source file and Django template files.

So any tips you come up with will be invaluable.  Please post
anything you learn to this thread.

Thanks!

--Fred

---

Fred Stluka -- mailto:fred@bristle.com -- http://bristle.com/~fred/
Bristle Software, Inc -- http://bristle.com -- Glad to be of service!
Open Source: Without walls and fences, we need no Windows or Gates.

---

On 3/30/16 9:23 AM, bobhaugen wrote:

We feel your pain. If you do it, and write down how it goes, we would be grateful.

https://github.com/valnet/valuenetwork

On Tuesday, March 29, 2016 at 4:19:59 PM UTC-5, Roger Dunn wrote:

I've inherited a moderately large project written 2 years ago using Django 1.4, and wondering if it is worth creating a fresh 1.9 project and porting in the old code, or doing an in-place upgrade to 1.9?

I have it running on 1.4 'as is' but if I run python manage.py migrate it comes unglued as a lot of stuff has changed since 1.4.

--
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+unsubscribe@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/2a3de1fc-5032-4807-b008-66f2e381ac7f%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 django-users+unsubscribe@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/56FBDDBE.9020409%40bristle.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 django-users+unsubscribe@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/CACczBU%2BhDnDtD4WwkAPGWc4W0Zq9wz-iK%3DdmcNn0ONAijG8feQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.