All ECOM-related services now run on Django 1.9.x <https://docs.djangoproject.com/en/1.9/releases/1.9/>. This update allows our services take advantage of some of the latest features and improvements of Django.
One immediate improvement will be shorter migration and test run times. Django 1.8 has a bug <https://code.djangoproject.com/ticket/24743> that results in long delays when gathering migrations. This bug has been fixed in Django 1.9, resulting in much shorter test run times. It is also worth noting that Django Oscar, used by the E-Commerce Service, has also been updated to version 1.4 to accommodate the latest version of Django. This update allows us to gain more experience and knowledge with Django 1.9 that will be applied when the time arises to upgrade edx-platform to the next LTS release of Django, 1.11. The following services have been upgraded: - Credentials - E-Commerce The Catalog Service already operates on Django 1.9. The Programs Service is being retired, so no upgrade has been applied. *FAQ* Why not upgrade to Django 1.10? > Upgrading from Django 1.9 to 1.10 is not as simple as editing the > requirements file and fixing deprecation issues. That upgrade will require > a bit more discovery. How does this affect OpenEdX? > If you are using an open source release, such as Ficus, keep doing what > you're doing. These updates will be in the Gingko release. > If you are working from a fork or the master branch, please see the > deployment issues note at > https://openedx.atlassian.net/wiki/display/COMM/Ginkgo for steps to > follow regarding faking a migration. Please post your questions or comments to this thread. Clinton Blackburn, Tech Lead edX ECOM/Learner Engineering -- You received this message because you are subscribed to the Google Groups "General Open edX discussion" group. To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/CAJ%3D5OMVXLE8iwtPdoM%3DvLJzYsk3Fdfx7%3DrkmtX97Y9nQzAxbmw%40mail.gmail.com.
