From Fedora Project Wiki
< Changes
(→Scope) |
Churchyard (talk | contribs) (Summary update, add myself to owners) |
||
| Line 3: | Line 3: | ||
<!-- 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 2.0 = | ||
== Summary == | == Summary == | ||
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. --> | <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. --> | ||
This change is about upgrading python-django to version 2.0. The latest Django release drops support for Python 2, but | This change is about upgrading {{package|python-django}} to version 2.0. The latest Django release [https://docs.djangoproject.com/en/2.0/releases/2.0/#python-compatibility drops support for Python 2], but a few Django apps packaged in Fedora do not yet support Python 3. | ||
not support Python 3. | |||
== Owner == | == Owner == | ||
| Line 16: | Line 15: | ||
--> | --> | ||
* Name: [[User:mrunge| Matthias Runge]] | * Name: [[User:mrunge| Matthias Runge]] | ||
* 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: <mrunge@matthias-runge.de> | * Email: <mrunge@matthias-runge.de> <mhroncok@redhat.com> | ||
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
Revision as of 13:21, 12 December 2017
Django 2.0
Summary
This change is about upgrading 
python-django
Owner
- Name: Matthias Runge
- Name: Miro Hrončok
- Email: <mrunge@matthias-runge.de> <mhroncok@redhat.com>
- Release notes owner:
Current status
- Targeted release: Fedora 28
- Last updated: 2017-12-12
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
The latest Django release 2.0 finally drops support for Python 2.7. Not all dependent applications can keep up with Djangos pace. This change describes a way how to enable both, keeping 2.7 compatibility and also leveraging the latest version.
Benefit to Fedora
Fedora will be able to provide both: latest and current release and also a fallback for applications, which do not support Python3 yet.
Scope
- Proposal owners: drop Python2 subpackage from python-django, upgrade python-django to Django-2.0 and package Django-1.11.x for Python2 only.
- Other developers: Other developers, whose applications do work with Python3 and Django 2.0 will need to change the requirement to python3-django.
- Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines:
- Python packaging guidelines
- Documentation should be provided
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
You should be able to install two web-apps, one requiring python2-django and one requiring python3-django. (TODO: provide actual package names)
- dnf install (package 1)
- see python2-django is installed as dependency
- run that package
- dnf install (package 2)
- verify python3-django is installed as dependency
- package 1 still works
- package 2 works as well
- dnf remove package 1
- package 2 still works
User Experience
N/A (not a System Wide Change)
Dependencies
N/A (not a System Wide Change)
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), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)