From Fedora Project Wiki
(Scope)
(Add tracking bug)
 
(4 intermediate revisions by the same user not shown)
Line 23: Line 23:
  
 
<!-- 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 -->
= Change Proposal Name Django18 =
+
= Django18 =
  
 
== 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. -->
  
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.
+
Update python-django to version 1.8.
 
 
Django upstream is transparent and announces deprecation far in advance. It should be possible for many
 
  
 
== Owner ==
 
== Owner ==
Line 44: Line 42:
 
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
 
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
 
-->
 
-->
 
  
 
== Current status ==
 
== Current status ==
Line 57: 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: <will be assigned by the Wrangler>
+
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1191053 #1191053]
  
 
== Detailed Description ==
 
== 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.
  
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+
Django upstream is transparent and announces deprecation far in advance.  
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
Line 68: Line 66:
  
 
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.  
 
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.  
 
 
    
 
    
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
 
 
== Scope ==
 
== Scope ==
 
* Proposal owners:  
 
* Proposal owners:  
Line 77: Line 73:
 
** 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.
 
** 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
 
** 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
 
* Other developers: update dependent packages to work with Django-1.8
  
* Release engineering: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Release engineering: N/A  
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
  
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Policies and guidelines: N/A
 
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
 
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
  
Line 111: Line 106:
  
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
 
== User Experience ==
 
== User Experience ==
 
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
Line 121: Line 115:
  
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
updates to dependent packages are required.
+
Updates to dependent packages are required.
  
 
== Contingency Plan ==
 
== Contingency Plan ==
Line 149: Line 143:
 
-->
 
-->
  
[[Category:ChangeReadyForWrangler]]
+
[[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

  • 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

Release Notes