...
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?
...
Learners and educators should see no change in site availability or functionality as a result of the upgrade. Some developers will assist in implementing it, and all should read Django 3.2 Upgrade: Key Changes for a summary of minor changes in how to write new application code as a result of the upgrade
...
. Site operators shouldn’t need to do anything beyond upgrading to the upcoming Maple release of Open edX, which most of them intend to do anyway.
How will we do it?
...
Path to production
...
Rollout plan
...
Will there be any downtime?
...
Rollback or another contingency plan
...
Each IDA can be upgraded independently whenever testing with Django 3.2 is complete. This can be done via the standard deployment pipeline and should require no downtime. If unexpected problems are hit in stage or production, a standard pipeline rollback can be used. Barring any such unexpected problems, the upgrade should be transparent to site users.
Scope
Upgrade all IDAs from Django 2.2 to 3.2 in production and Edge:
...