Bug 461327

Summary: Django 1.0 Released
Product: [Fedora] Fedora Reporter: Steve Milner <smilner>
Component: DjangoAssignee: Michel Lind <michel>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: esm, marco.crosio
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://www.djangoproject.com/weblog/2008/sep/03/1/
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-25 00:00:05 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 Steve Milner 2008-09-05 21:47:19 UTC
Django 1.0 has been released http://www.djangoproject.com/download/1.0/tarball/). :-)

Side note, if you are looking for a co-maintainer I wouldn't mind helping out ... I'd love to see Django get into EPEL.

Comment 1 Michel Lind 2008-09-05 23:27:41 UTC
They sure move fast. Sure thing about co-maintaining, just apply for the ACLs you want over at pkgdb?

Comment 2 Fedora Update System 2008-09-06 14:36:28 UTC
Django-1.0-1.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/Django-1.0-1.fc9

Comment 3 Fedora Update System 2008-09-06 14:52:00 UTC
Django-1.0-1.fc8 has been submitted as an update for Fedora 8.
http://admin.fedoraproject.org/updates/Django-1.0-1.fc8

Comment 4 Fedora Update System 2008-09-11 16:55:03 UTC
Django-1.0-1.fc9 has been pushed to the Fedora 9 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update Django'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-7777

Comment 5 Fedora Update System 2008-09-11 17:06:17 UTC
Django-1.0-1.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update Django'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-7901

Comment 6 Steve Milner 2008-09-15 17:06:24 UTC
(In reply to comment #1)
> They sure move fast. Sure thing about co-maintaining, just apply for the ACLs
> you want over at pkgdb?

Requested via pkgdb.

Comment 7 Fedora Update System 2008-09-25 00:00:02 UTC
Django-1.0-1.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2008-09-25 00:13:40 UTC
Django-1.0-1.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Ed Marshall 2008-09-25 12:49:56 UTC
Ouch, 1.0 is backwards-incompatible with 0.96; wouldn't it have been a good idea to hold off until F10 for this? This certainly isn't something I was expecting to see, and I suspect others might be surprised by it as well.

Comment 10 Ed Marshall 2008-09-25 12:54:49 UTC
More information on porting from 0.96 (the previous release in F8 and F9) and 1.0:

http://docs.djangoproject.com/en/dev/releases/1.0-porting-guide/

"Django 1.0 breaks compatibility with 0.96 in some areas." Anyone who just updated blindly bought themselves more than a few minutes with that documemnt.

Comment 11 Michel Lind 2008-09-25 13:41:50 UTC
Uh yes. That probably would have been (In reply to comment #9)
> Ouch, 1.0 is backwards-incompatible with 0.96; wouldn't it have been a good
> idea to hold off until F10 for this? This certainly isn't something I was
> expecting to see, and I suspect others might be surprised by it as well.

In hindsight, you're probably right. I was weighing off between F8 going EOL with a Django prerelease (albeit stable) and pushing backward-incompatible changes to users. Given that the development team still backport changes all the way back to 0.95, staying with 0.96 might have been better.

Well, now that the cat is out of the bag, as a test sample of size 1, would you prefer a downgrade back to 0.96 (which requires every subsequent Django package to be epoch-bumped), a Django096 compatibility RPM for 0.96 users, or install Django 0.96 from tarball?

Thanks, and sorry for the inconvenience.