From Fedora Project Wiki
(Change approved by FESCo https://pagure.io/fesco/issue/2239#comment-602387)
(Add trackers)
 
Line 40: Line 40:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1758690 #1758690]
* Release notes tracker: <will be assigned by the Wrangler>
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/401 #401]


== Detailed Description ==
== Detailed Description ==

Latest revision as of 21:14, 4 October 2019


Django 3

Summary

This change is about upgrading Package-x-generic-16.pngpython-django to version 3.0. A compatibility package is not planned (but it is part of the contingency plan).

Owner


Current status

Detailed Description

The Package-x-generic-16.pngpython-django package will be updated to 3.0.

Django 3.0 begins the journey to making Django fully async-capable by providing support for running as an ASGI application.

This is in addition to the existing WSGI support. Django intends to support both for the foreseeable future. Async features will only be available to applications that run under ASGI, however.


Benefit to Fedora

Fedora will be able to provide the latest and current release of Django.


Scope

  • Django libraries/apps owners: Test that your packages work with Django 3. Update, contact upstream for help. Retire leaf packages with libraries if not compatible.
  • Release engineering: no impact with Release Engineering is anticipated
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

List of packages directly requiring Package-x-generic-16.pngpython3-django:

Upgrade/compatibility impact

Eventually removed packages need to be obsoleted.

How To Test

  1. dnf update python3-django

Test that Fedora packaged Django applications still function as before, open Bugzillas if they don't.

User Experience

Users using RPM installed Django to develop Django apps might be affected by this change. We shall recommend either using Python venvs for users who develop Django apps. See the developer portal, we are already recommending that.

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) Proposal owners will introduce a python-django2 compatibility package if everything goes south.
  • Contingency deadline: beta freeze
  • Blocks release? No
  • Blocks product? No

Documentation

  1. https://docs.djangoproject.com/en/3.0/releases/3.0/

Release Notes

TBD