From Fedora Project Wiki

Django 6.x

Summary

Update the default Django stack in Fedora from 5.x to 6.x

Owner

Current status

Detailed Description

Following the plan laid out in Changes/Django_5x, we will package python-django6 for the upcoming Fedora 44 and look into branching it for Fedora EPEL 10. On Fedora 44 this will simply be installable as python3-django and users on previous Fedora releases will be upgraded; on older Fedora releases (if we decide to release) this will be installable as python3-django6, and likewise on EPEL 10. Some dependencies will be updated. python-django5 which currently provides the default python3-django on Fedora 42 and Fedora 43 will be modified to produce python3-django5 instead.

While 6.0 is not an LTS, Django does not break compatibility within a major version and the upcoming 6.2 LTS will be supported until April 2030, while 5.2 LTS will only be supported until April 2028; see upstream's supported versions documentation.


Feedback

Benefit to Fedora

Users can make use of the latest Django version; users who use Django add-ons that are not ready for 6.0 yet can switch it out for python3-django5.

Our mailing list infrastructure currently runs on EL9 with Django 4.2, and skipping 5.2 to go straight to Django 6 for EL10 buys us two more years of support - it will be supported until comfortably after EL 11 comes out.

Scope

  • Proposal owners: update Django 6 dependencies (aiosmtpd, asgiref) and review Django 6. We plan to upgrade asgiref step by step in Rawhide to allow us to pick an appropriate branching point for EPEL 10.
  • Other developers: N/A, though we will be working with the infra team should try testing this on EL10 and make sure the Django add-ons we need are compatible or made compatible before switching over to EL10.
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with the Fedora Strategy:

Upgrade/compatibility impact

Fedora systems with python3-django installed and no incompatible Django add-ons will upgrade just fine. If you have incompatible add-ons you should get upgraded to python3-django5 instead - we will test this update path.

If we hit unexpected issues we can make python-django6 provide python3-django6 instead on Fedora 44 and delay making it the default for a release.

Early Testing (Optional)

Do you require 'QA Blueprint' support? N/A

How To Test

  • Install python3-django on Fedora 43, try upgrading to Rawhide, make sure it works
  • Install additional packages dependent on Django, repeat
  • Install additional packages compatible only with Django 5.x, repeat, make sure you end up with python3-django5 installed on Rawhide


User Experience

Users can benefit from new Django 6.x features

Dependencies

N/A

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) Make python-django6 produce python3-django6 instead and defer making it the default
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No


Documentation

N/A (not a System Wide Change)

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Django_6.x&oldid=765031"