On 27 Aug 06:34, David Spreen wrote: > Hello, > > the Django project will release their version 1.0 in the beginning of > next week. I know that usually no new upstream versions are allowed into > Lenny at this point. I wonder though if Django could be an exception.
That'd involve asking the RMs - I have no problems with someone trying to get it in, but I'd have thought getting an exception now would be very unlikely... > 1. Django has a significant Debian user-base (638 pop contest > installations when I last checked). That's not a bad count :) > 2. It is unlikely that version 0.96 will receive ongoing security > support from upstream for long after 1.0. That, as you've discovered from the django list, isn't quite true ;) They support for long period, we had an update to 0.95 in etch, for example... > 3. Due to changes in the admin and form applications, Django 1.0 will be > backwards incompatible with 0.96 and the old stable version's use in > Debian might be questionable. There's also backwards incompatibilities between 0.95 and 0.96 that will need addressing in some way when people upgrade... > 4. All packages that use Django are under our control (currently only in > experimental). > > Let me know what you think and how to best approach the release managers > with this. > > Most importantly, you can help this effort by testing the > python-django_1.0~beta1-1 package that is currently in experimental. I > am already using it in my own work. I'm still using 0.96 at the moment, but will be switching to 1.0 over the next week (as it'll be released then, hopefully!)... There's going to need to be a set of notes for the main backwards incompatible changes in the package, and a pointer to the django wiki page for the rest. Cheers, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
