Is an upgrade from 1.6 to 1.11 as complicated as migrating from 1.1 to 1.6?

53 views
Skip to first unread message

NoviceSortOf

unread,
May 16, 2017, 8:21:11 AM5/16/17
to Django users

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 

Mike Dewhirst

unread,
May 16, 2017, 8:29:43 AM5/16/17
to django...@googlegroups.com
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
--
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...@googlegroups.com.
To post to this group, send email to django...@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.
For more options, visit https://groups.google.com/d/optout.

Andréas Kühne

unread,
May 16, 2017, 9:11:51 AM5/16/17
to django...@googlegroups.com
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 <dljons...@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+unsubscribe@googlegroups.com.
--
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...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.

Darrell Jonsson

unread,
May 16, 2017, 9:43:37 AM5/16/17
to django...@googlegroups.com

Thanks Andreas,

Looking at the docs its seems upgrading to 1.11 LTS would give us the
longest
future in terms of updates. Is there any reason we should consider 1.10
over 1.11?

Thanks


On 5/16/2017 3:11 PM, Andréas Kühne wrote:
> 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
> <mailto: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 <dljons...@gmail.com
> <mailto:dljons...@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...@googlegroups.com
> <mailto:django-users...@googlegroups.com>.
> To post to this group, send email to django...@googlegroups.com
> <mailto:django...@googlegroups.com>.
> Visit this group at https://groups.google.com/group/django-users
> <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
> <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...@googlegroups.com
> <mailto:django-users...@googlegroups.com>.
> To post to this group, send email to django...@googlegroups.com
> <mailto:django...@googlegroups.com>.
> Visit this group at https://groups.google.com/group/django-users
> <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
> <https://groups.google.com/d/optout>.
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Django users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/django-users/9CuRMH1vyqQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> django-users...@googlegroups.com
> <mailto:django-users...@googlegroups.com>.
> To post to this group, send email to django...@googlegroups.com
> <mailto:django...@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
> <https://groups.google.com/d/msgid/django-users/CAK4qSCe6MHRuvEe4_5cRZm9TSXfa6gCgcLwOAsoqjQy1ttHa5w%40mail.gmail.com?utm_medium=email&utm_source=footer>.

NoviceSortOf

unread,
May 16, 2017, 9:51:47 AM5/16/17
to Django users
Thanks Mike, I might take you up on the 1.6 to 1.8.18 upgrade idea.

Andréas Kühne

unread,
May 16, 2017, 10:22:12 AM5/16/17
to django...@googlegroups.com
The main problem is as I said earlier your implementation. There COULD be things that you use (like packages that aren't upgraded or code that doesn't work) which make the upgrade to 1.11 harder. But it should absolutely be possible. 

I would consider trying to get to 1.11 as it's like you said an LTS. 

Going from 1.11 to 2.0 could be harder though - as 2.0 will ONLY support python 3.

Regards,

Andréas


    To post to this group, send email to django...@googlegroups.com

    --     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,

    To post to this group, send email to django...@googlegroups.com
To unsubscribe from this group and all its topics, send an email to django-users+unsubscribe@googlegroups.com <mailto:django-users+unsubscrib...@googlegroups.com>.
To post to this group, send email to django...@googlegroups.com <mailto:django-users@googlegroups.com>.
--
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...@googlegroups.com.

Derek

unread,
May 17, 2017, 11:59:51 AM5/17/17
to Django users, jon...@well.com
What I found was that many third-party apps did not (yet) seem to support 1.11.  So a move to 1.10 was most pragmatic for us, with the assumption that migrating to 1.11 would be straightforward in about a year or so.  And, yes, work in Python 3 unless a very good reason not to.

 
>     To post to this group, send email to django...@googlegroups.com
>     <mailto:django...@googlegroups.com>.
>     Visit this group at https://groups.google.com/group/django-users
>     <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
>     <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...@googlegroups.com
>     To post to this group, send email to django...@googlegroups.com
>     <mailto:django...@googlegroups.com>.
>     Visit this group at https://groups.google.com/group/django-users
>     <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
>     <https://groups.google.com/d/optout>.
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Django users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/django-users/9CuRMH1vyqQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> django-users...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages