(Change Announced on 2015-01-20) |
(Add tracking bug) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 54: | Line 54: | ||
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=1191053 #1191053] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 143: | Line 143: | ||
--> | --> | ||
[[Category: | [[Category:ChangeAcceptedF22]] | ||
<!-- 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 11:40, 10 February 2015
Django18
Summary
Update python-django to version 1.8.
Owner
- Name: Matthias Runge
- Email: <mrunge@fedoraproject.org>
- Release notes owner:
Current status
Detailed Description
Update python-django to version 1.8. Fedora 21 contains version 1.6, which will become deprecated by upstream, once Django-1.8 is out. This is a change, impacting many of python-django-* packages.
Django upstream is transparent and announces deprecation far in advance.
Benefit to Fedora
Current Django versions in Fedora are just short term supported. For Django-1.8, upstream writes (https://docs.djangoproject.com/en/dev/releases/1.8/):
Django 1.8 has been designated as Django’s second “Long-Term Support” (LTS) release. It will receive security updates for at least three years after its release. Support for the previous LTS, Django 1.4, will end 6 months from the release date of Django 1.8.
Scope
- Proposal owners:
- update python-django to version 1.8. To support maintainers of dependent packages, a copr repo containing latest Django-1.8 is here: https://copr.fedoraproject.org/coprs/mrunge/django-1.8/
- A build containing latest Django will be pushed to f22 branch late in dev cycle. If we decide not to push Django-1.8, nothing will be broken.
- Django 1.8 final release is expected around April 1st, 2015: https://code.djangoproject.com/wiki/Version1.8Roadmap#schedule
- Other developers: update dependent packages to work with Django-1.8
- Release engineering: N/A
- Policies and guidelines: N/A
Upgrade/compatibility impact
A list of incompatible changes for Django-1.8 can be found her: https://docs.djangoproject.com/en/dev/releases/1.8/#features-deprecated-in-1-8
How To Test
This is not about adding a new feature, but updating a set of packages. A test is successful, when packages are still working after the change.
User Experience
No user interaction should be required for updating python-django itself. It may be possible, configure changes for dependent packages are required.
Dependencies
Updates to dependent packages are required.
Contingency Plan
- Contingency mechanism: If we can not make it, we'll keep Django-1.7 from rawhide.
- Contingency deadline: Fedora 22 Beta release.
- Blocks release? No
- Blocks product? doesn't block a product.
Documentation
Upstream release notes: https://docs.djangoproject.com/en/dev/releases/1.8/
The list of deprecated features is here: https://docs.djangoproject.com/en/dev/internals/deprecation/#deprecation-removed-in-1-8