This is a tracking bug for Change: Django 2.0
For more details, see: https://fedoraproject.org//wiki/Changes/Django20
This change is about upgrading python-django to version 2.0. The latest Django release drops support for Python 2, but a few Django apps packaged in Fedora do not yet support Python 3. A compatibility package will be provided for those.
On 2018-Feb-20, we have reached the Fedora 28 Change Checkpoint: Completion deadline (testable).
At this point, all accepted changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be enabled at Change Completion deadline as well.
Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness.
Incomplete and non testable Changes will be reported to FESCo for 2018-Feb-23 meeting.
A substantial part of the packages have been changed, django-2.0 has been built and pushed to rawhide, incompatible packages were either fixed or retired.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.
On 2018-Mar-08 we reached the "Change Checkpoint: 100% Code Complete Deadline" milestone for Fedora 28 release. At this point all the Changes not at least in "ON_QA" state should be brought to FESCo for review. Please update the state of this bug to "ON_QA" if it is already 100% completed. Please let me know in case you have any trouble with the implementation and the Change needs any help or review.
Current state, the following packages need action:
Maintainers by package:
python-django-fas jdornak (ready in master git only)
python-django-federated-login echevemaster lbazan
python-django-post_office ankursinha (built for rawhide only)
python-django-south diegobz jdornak lbazan
Packages by maintainer:
echevemaster python-django-ckeditor python-django-federated-login python-django-select2
jdornak python-django-fas python-django-markdown2 python-django-sekizai python-django-south
lbazan python-django-federated-login python-django-helpdesk python-django-setuptest python-django-south
rmarko python-django-extensions python-django-openid-auth
python-django-ckeditor: the rpm package was not updated/changed by the package maintainer. However, upstream provides a version compatible with django-2.0
python-django-extensions: it is compatible to django2.0 upstream, but the rpm maintainer did not update it yet
python-django-federated-login should be retired. It hasn't seen a upstream release for 4 years
python-django-helpdesk hasn't touched by the owner in ages, it has experimental django-2.0 support upstream
python-django-markdown2 had yesterday an upstream release, it supports python3
python-django-openid-auth: last release upstream: 2017-04-03, unclear support of both django-2.0 and python3
python-django-pgjson: latest upstream release, 4 years ago. Maybe it's time to drop the package?
python-django-pylibmc: supports django 2.0 and python-3.6 upstream, but hasn't had a release for > 2 years.
python-django-sekizai: a bit aged in fedora, but even upstream does not support anything newer than django 1.10. Time for retire?
python-django-setuptest hasn't seen a release in 2 years upstream. It doesn't support django-1.8; it should be retired
python-django-select2: outdated in fedora, upstream supports django-2.0, and python3
python-django-south: it does not work with django-1.7 and later. request to retire it: rhbz# 1547082
Got approval from jdornak for retirement of sekizai and south.
python-django-pgjson has been retired.
As per FESCo's decision in https://pagure.io/fesco/issue/1861 all packages not fixed by next Friday (2018-03-16) will be retired.
$ dnf repoquery --releasever 28 --whatrequires python2-django
FTBFS (test failure on python3 with django2)!
$ dnf repoquery --releasever 28 --whatrequires python-django
I consider this testable with 3 known bugs.
Do the three bugs have issues? I see one open bug blocking this one.
Added 3 bugs that block this.
All component bugs are resolved, so this one is done too.
Thanks everybody involved.