Bug 802154

Summary: Possibility of Django 1.3 update in epel6?
Product: [Fedora] Fedora EPEL Reporter: Kevin Fenzi <kevin>
Component: DjangoAssignee: Steve Milner <smilner>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: el6CC: a.badger, dmalcolm, michel, mrunge, sgallagh, smilner
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-11 18:09:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kevin Fenzi 2012-03-11 18:09:15 UTC
Is there any chance of upgrading Django to 1.3.x in epel6? 

There do seem to be some incompatible changes: https://docs.djangoproject.com/en/dev/releases/1.3/#backwards-incompatible-changes-1-3

But I'm not sure how incompatible they are in practice. 

https://docs.djangoproject.com/en/1.2/internals/release-process/
seems to say that 'minor' updates should be compatible. 

In Fedora Infrastructure we have reviewboard and askbot using Django, and both of them would work fine with 1.3.x I am pretty sure. 

Thoughts?

Comment 1 Kevin Fenzi 2012-03-11 18:09:49 UTC

*** This bug has been marked as a duplicate of bug 802153 ***