F44 Change Proposal: Django 6.x [SelfContained]

Project Discussion Change Proposals
, ,
1

Django 6.x

Wiki

Announced

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary :open_book:

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

Owner :open_book:

  • Name: [[User:salimma|Michel Lind]], [[User:carlwgeorge|Carl George]]
  • Email: michel@michel-slm.name, carl@redhat.com

Detailed Description :open_book:

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 [Download Django | Django supported versions] documentation.

Feedback :open_book:

Benefit to Fedora :open_book:

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 :open_book:

  • Proposal owners: update Django 6 dependencies ([Making sure you're not a bot! 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.
  • Release engineering: [Making sure you're not a bot! #Releng issue number]
  • 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 :open_book:

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) :open_book:

Do you require ‘QA Blueprint’ support? N/A

How To Test :open_book:

  • 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 :open_book:

Users can benefit from [Django 6.0 release notes | Django documentation | Django new Django 6.x features]

Dependencies :open_book:

N/A

Contingency Plan :open_book:

  • 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 :open_book:

N/A (not a System Wide Change)

Release Notes :open_book:

\n

Last edited by @alking 2026-01-12T18:16:38Z

Last edited by @alking 2026-01-12T18:16:38Z

2

How do you feel about the proposal as written?

  • Strongly in favor
  • In favor, with reservations
  • Neutral
  • Opposed, but could be convinced
  • Strongly opposed
0 voters

If you are in favor but have reservations, or are opposed but something could change your mind, please explain in a reply.

We want everyone to be heard, but many posts repeating the same thing actually makes that harder. If you have something new to say, please say it. If, instead, you find someone has already covered what you’d like to express, please simply give that post a :heart: instead of reiterating. You can even do this by email, by replying with the heart emoji or just “+1”. This will make long topics easier to follow.

Please note that this is an advisory “straw poll” meant to gauge sentiment. It isn’t a vote or a scientific survey. See About the Change Proposals category for more about the Change Process and moderation policy.

3

This change proposal has now been submitted to FESCo with ticket #3557 for voting.

To find out more, please visit our Changes Policy documentation.

4

This change has been approved by FESCo and will be included in Fedora Linux 44.
To find out more about how our changes policy works, please visit our docs site.

FESCo Issue: Making sure you're not a bot!