By upgrading directly from 1.4 to 1.11, deprecation warning might be
missed, resulting in a non-working project with few indication of what
is wrong.
2017-03-07 13:07 GMT+01:00 Antonis Christofides :
> There is no inherent reason for doing it a step at a time; you can go
> directly to 1.11 (which,
Here's the "official advice":
https://docs.djangoproject.com/en/dev/howto/upgrade-version/
On Tuesday, March 7, 2017 at 6:55:22 AM UTC-5, BIJAL MANIAR wrote:
>
>
> Hi,
>
> Currently we have an application built using django 1.4.
> As the latest LTS release is 1.11, we are planning to upgrade it
There is no inherent reason for doing it a step at a time; you can go directly
to 1.11 (which, btw, hasn't been released yet, it's in alpha I think, so it may
or may not be ok for you).
Doing it in steps might be better if you intend to read the release notes. So
you read the release notes for 1.5
Hi,
Currently we have an application built using django 1.4.
As the latest LTS release is 1.11, we are planning to upgrade it to 1.11.
Which of the below 3 alternatives is a better option for django version
upgrade.
1. Should we take it one release at a time? ie, Make the jump from 1.4 to
1.5
4 matches
Mail list logo
