Churchyard (talk | contribs) m (Change Ready For Wrangler) |
(Add trackers) |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 15: | Line 15: | ||
--> | --> | ||
* Name: [[User:churchyard| Miro Hrončok]] | * Name: [[User:churchyard| Miro Hrončok]] | ||
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | ||
* Email: <mhroncok@redhat.com> | * Email: <mhroncok@redhat.com> | ||
* Name: [[User:mrunge| Matthias Runge]] | |||
* Email: <mrunge@redhat.com> | |||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | ||
--> | --> | ||
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) | <!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) | ||
* Product: | * Product: | ||
Line 37: | 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: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1758690 #1758690] | ||
* Release notes tracker: | * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/401 #401] | ||
== Detailed Description == | == Detailed Description == | ||
Line 179: | Line 182: | ||
TBD | TBD | ||
[[Category: | [[Category:ChangeAcceptedF32]] | ||
<!-- 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 --> |
Latest revision as of 21:14, 4 October 2019
Django 3
Summary
This change is about upgrading python-django
to version 3.0. A compatibility package is not planned (but it is part of the contingency plan).
Owner
- Name: Miro Hrončok
- Email: <mhroncok@redhat.com>
- Name: Matthias Runge
- Email: <mrunge@redhat.com>
Current status
- Targeted release: Fedora 32
- Last updated: 2019-10-04
- Tracker bug: #1758690
- Release notes tracker: #401
Detailed Description
The python-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
- Proposal owners: upgrade
python-django
to 3.0 prerelease as soon as this change is accepted (pull request).
- 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 python3-django
:
graphite-web
kobo
python-django-ajax-selects
python-django-angular
python-django-annoying
python-django-appconf
python-django-authority
python-django-babel
python-django-cacheops
python-django-compressor
python-django-contact-form
python-django-cors-headers
python-django-database-url
python-django-debreach
python-django-debug-toolbar
python-django-filter
python-django-formtools
python-django-haystack
python-django-helpdesk
python-django-js-asset
python-django-jsonfield
python-django-macros
python-django-markdownx
python-django-mptt
python-django-nose
python-django-pipeline
python-django-post_office
python-django-pyscss
python-django-pytest
python-django-redis
python-django-registration
python-django-rest-framework
python-django-rest-framework-composed-permissions
python-django-reversion
python-django-robots
python-django-rq
python-django-simple-captcha
python-django-tables2
python-django-tagging
python-django-taggit
python-django-tastypie
python-django-threadedcomments
python-django-timezone-field
python-django-tinymce
python-djangoql
python-livereload
python-pelican
python-whitenoise
python3-openid
Upgrade/compatibility impact
Eventually removed packages need to be obsoleted.
How To Test
- 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
Release Notes
TBD