This page is still under construction.
All of the Django-using Open edX IDAs are now on Django 2.2, which will reach end of life in April 2022. edX wants to upgrade Django to version 3.2, the next LTS (long term support) release. We want this project complete by October 15, 2021, in time for the next Open edX release, Maple. Key contacts are Jeremy Bowman (Deactivated) and Natalia Berdnikov (Deactivated).
What is this about?
Briefly describe service and its role and impact on our systems.
Who owns it within edX?
What do we plan to do with it in a nutshell?
Is this a small, medium or large project (ballpark)?
Any other relevant context to help understand importance, size or impact.
Why are we doing this?
Why does this need to be done? What is the impact of not doing this?
Could we better of not doing it, postponing, retiring the service, or replacing it with another?
Why did we pick this version to upgrade to?
Why does this need to be done now?
Can someone else do this for us?
Have we done this before?
Have we done this before for in edX.org instance or for any other Open edX instance?
Did the last time go well?
Do we want to do things differently this time, and how?
Provide links to wiki pages of similar previous projects
What do we plan to do?
What is the scope of this project?
On high level, what is our plan? Identify big milestones.
Who do we plan to involve (groups of stakeholders)?
Are there risks and dependencies?
Are there any known risks?
How can we mitigate them?
Have we reviewed system requirements (e.g. AWS, Python, etc.) for this upgrade?
Are there dependencies with other projects?
Are there any third-party integrations that might be affected by this upgrade? What other systems or services rely on this service?
What is the impact of this upgrade on various users of the system?
Which user groups or personas will this upgrade impact? E.g. developers, learners, educators, site operators, etc.
Are there any new features?
Are there any features or functionality that are being removed as a result of the upgrade?
How will we do it?
Path to production
Rollout plan
Will there be any downtime?
Do end users of the edX website need to be notified?
Scope
Upgrade all IDAs from Django 2.2 to 3.2 in production and Edge:
Review dependencies and ensure all things we use are upgraded to 3.2 or we no longer use them.
Run scripts to automatically fix known problems (apply code mods)
Update the test suites for repositories so they can work on all of the following Django versions: 2.2, 3.0, 3.1, and 3.2. Test, and fix identified problems.
Upgrade the default version of the IDA to be 3.2 and test
[Can be done after Maple, if necessary] Drop testing Django 2.2, 3.0 and 3.1 in all IDAs
Notes:
You’re least likely to get blocked by unfinished work if you first upgrade repositories that have the fewest dependencies.
Roll out upgrades to IDAs one by one, as they are ready.
A more detailed description of the steps involved can be found in Django 3.2 Upgrade: Steps to Upgrade a Repository.