Many thanks to you all guys, I will follow this path.
Alan
On 27 January 2017 at 22:05, bobhaugen wrote:
> I agree with all the advice to go a step at a time.
>
> Here's a bunch of clues and chatter in github issues about how we upgraded
> from 1.4 to 1.8, one minor version at a time.
> https:/
I agree with all the advice to go a step at a time.
Here's a bunch of clues and chatter in github issues about how we upgraded
from 1.4 to 1.8, one minor version at a time.
https://github.com/FreedomCoop/valuenetwork/issues?q=is%3Aclosed+label%3Aupgrade
--
You received this message because you
I'd advise you to be aware of third-party libraries. Sometimes they are
dropped or can bring some incompatibilities.
On 27 January 2017 at 08:42, Andreas Kuhne
wrote:
> I second this. Having moved from 1.3 to 1.9 in stages - I think this is
> the best way to do it. Upgrade one minor version at a
I second this. Having moved from 1.3 to 1.9 in stages - I think this is the
best way to do it. Upgrade one minor version at a time and it will probably
be easiest.
Regards,
Andréas
2017-01-27 10:55 GMT+01:00 ludovic coues :
> You might have an easier time upgrading from one version to the next.
You might have an easier time upgrading from one version to the next.
So first check if you have some deprecation warning and fix them. Then
install django 1.4, check if you have deprecation warnings, fix them.
Check things are working as intended. Test really help at this point.
Once you are run
Hi there,
Sorry for this question, we have created this service 5 years ago and never
touched since but now we want to move to a new server, with all updated
software and even use python 3.5, I am wondering if there's any kind of
"how-to" for it.
Any help/suggestion is really appreciated.
Thanks
6 matches
Mail list logo