Skip to content

Django 5.2 Upgrade #339

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
feanil opened this issue Apr 4, 2025 · 0 comments
Open

Django 5.2 Upgrade #339

feanil opened this issue Apr 4, 2025 · 0 comments

Comments

@feanil
Copy link
Contributor

feanil commented Apr 4, 2025

Overview

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.

@feanil feanil moved this to In Progress in Maintenance Apr 4, 2025
@feanil feanil moved this to Being Developed in Open edX Roadmap Apr 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Status: Being Developed
Development

No branches or pull requests

1 participant