< Changes
No edit summary |
(Announcing the Change proposal) |
||
| Line 2: | Line 2: | ||
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | ||
= | = Django 4.0 = | ||
== Summary == | == Summary == | ||
| Line 16: | Line 16: | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeAnnounced]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
| Line 34: | Line 34: | ||
ON_QA -> change is fully code complete | ON_QA -> change is fully code complete | ||
--> | --> | ||
* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/W7JK2LLQ33SIFNSQB5OOBRTGTUHAYVFE/ devel thread] | |||
* FESCo issue: <will be assigned by the Wrangler> | * FESCo issue: <will be assigned by the Wrangler> | ||
* Tracker bug: <will be assigned by the Wrangler> | * Tracker bug: <will be assigned by the Wrangler> | ||
| Line 100: | Line 101: | ||
* Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: N/A (not a System Wide Change) | * Contingency deadline: N/A (not a System Wide Change) | ||
* Blocks release? N/A (not a System Wide Change) | |||
* Blocks release? N/A (not a System Wide Change) | |||
| Line 109: | Line 109: | ||
Extensive upstream documentation can be found at https://docs.djangoproject.com/en/4.0/ | Extensive upstream documentation can be found at https://docs.djangoproject.com/en/4.0/ | ||
== Release Notes == | == Release Notes == | ||
Revision as of 16:27, 5 January 2022
Django 4.0
Summary
Update Django to version 4.0.
Owner
- Name: Matthias Runge
- Email: mrunge@redhat.com
Current status
- Targeted release: Fedora Linux 36
- Last updated: 2022-01-05
- devel thread
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
The Django project has regular releases about every 9 months. Django 4.0 is a major milestone, and this Change will bring the Fedora included version to the latest version.
The immediate step is to bump the python-django package to version 4.0. It is expected, that dependent packages will be updated as well, or retired, if they haven't seen an update for long time.
Feedback
Benefit to Fedora
This updates to the latest Django version and allows to use the distribution provided version to be used both in new developments and also with latest Django applications.
The upstream project has more info on what's new https://www.djangoproject.com/weblog/2021/dec/07/django-40-released/
The risk of not completing this change is that the next update will be more disruptive, Django 4.1 is planned for about the same time as Fedora 37 will land.
Scope
- Proposal owners: python-django will be updated to version 4.0.
- Other developers:
Other developers or maintainers will have to test their packages with Django 4.0.
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
How To Test
The python3-django package has to be installed in order to run the test.
django-admin --version 4.0
Dependencies
Django (the fedora package name is python-django) has a few dependent packages which should get updated (or removed) as noted above. If they were not updated for Django 4.0, that probably means that their upstream is not very active anymore.
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change)
Documentation
Extensive upstream documentation can be found at https://docs.djangoproject.com/en/4.0/