Bug 1186020

Summary:	Update Request: python-django 1.7
Product:	[Fedora] Fedora EPEL	Reporter:	Pat Riehecky <riehecky>
Component:	python-django	Assignee:	Matthias Runge <mrunge>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	bkabrda, jdornak, mhroncok, michel, mrunge
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-27 08:24:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pat Riehecky 2015-01-26 20:24:34 UTC

Description of problem:
The release of Django 1.7 provides a number of enhancements to applications and data migrations.

It would be nice to have this more recent version packaged within EPEL-7

Version-Release number of selected component (if applicable):python-django-1.6.10-1.el7


How reproducible: 100%


Steps to Reproduce:
1.request for new version
2.
3.

Actual results:


Expected results:


Additional info:
https://docs.djangoproject.com/en/1.7/releases/1.7/

Comment 1 Matthias Runge 2015-01-27 08:24:23 UTC

Thanks for your report.

We currently have Django-1.7 for upcoming Fedora 22 version. 

Please understand, there is a stable policy intact, which prevents me from upgrading Django. The issue is, I'll break at least some of the included applications depending on Django in EPEL7.

However, I'm planning to upgrade to Django-1.8, once that is released in March/early April, as that is the designated successor of last long term supported version Django-1.4.

Comment 2 Matthias Runge 2015-01-27 08:35:04 UTC

A copr repo containing latest Django-1.8 builds is here:
https://copr.fedoraproject.org/coprs/mrunge/django-1.8/