Bug 802154 - Possibility of Django 1.3 update in epel6?
Summary: Possibility of Django 1.3 update in epel6?
Keywords:
Status: CLOSED DUPLICATE of bug 802153
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: Django
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Milner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-11 18:09 UTC by Kevin Fenzi
Modified: 2012-03-11 18:09 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-11 18:09:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.