You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Django upgrade will be performed on all repositories that use Django starting with the libraries and working our way up to the services. The effort will rely on repository maintainers to shepherd the upgrade process.
Approach
⭐ First phase: Update all openedx libraries to support Django 5.2 while maintaining 4.2 compatibility
✨ Second phase: Upgrade Django services to run exclusively on 5.2
Key Dates 📅
This week: 📝 Ticket creation and documentation for using django-upgrade
May 14, 2025: ⭐ All openedx libraries compatible with both Django 4.2 and 5.2
August 4, 2025: ✨ All openedx services running on Django 5.2
September 4, 2025: 📦 Tutor updates completed
Responsibilities
👩💻 Maintainers: Update your repositories
🦸 Maintainers-at-large: Handle repositories without assigned maintainers
🧭 Coordination: @Awais_Qureshi and I will be coordinating the overall upgrade
Questions? 💬
Direct questions about schedule changes, upgrade issues, or knowledge sharing to this thread. We’re here to help each other succeed! For additional support, contact @Awais_Qureshi or me.
The team here has fixed Django 5.2 support issues in edx-platform. We are currently using the DJANGO_STORAGES cherry-pick commit to keep tests running on Django 5.2, and all tests are green. Once DJANGO_STORAGES is merged, we will verify again through sandbox creation and smoke testing.
Activity
82 remaining items
awais786 commentedon Aug 3, 2025
We need review on these PR to ublock
edx-platformupgrade.kdmccormick commentedon Aug 21, 2025
Update from 8/21: Main blocker is DJANGO_STORAGES PR in edx-platform. The solution of that will be used as a template in multiple repositories.
awais786 commentedon Sep 4, 2025
The team here has fixed
Django 5.2support issues inedx-platform. We are currently using theDJANGO_STORAGEScherry-pick commit to keep tests running onDjango 5.2, and all tests are green. OnceDJANGO_STORAGESis merged, we will verify again through sandbox creation and smoke testing.DJANGO_STORAGESPR in review PR #2844@feanil FYI
feanil commentedon Mar 19, 2026
This upgrade is complete, we need to drop 4.2 support still but we can close this issue.