Upcoming Django release, and the future As we sit here in warm, sunny Dallas, meditating on how next year's PyCon will be in cold, cloudy Chicago, we're also getting ready to push out a new release of Django, and with that there are some things you all need to know, and as your friendly neighborhood release manager it's my job to tell you :)
First, the immediate future: the goal of the first part of our PyCon sprint this year is to get Django 0.96 rolled and released. There's a lot of cool new stuff that's landed in trunk since 0.95 (like the testing framework and the newforms library), and we want to get it out in an official release. If there's a bug that's been annoying the heck out of you and you want it fixed before the release, this would be the time to speak up about it. We have a fairly high concentration of Django developers all in one place with nothing to do but code, so hopefully we'll be able to hit a lot of stuff and get a release out very quickly (we'd like to release 0.96 in the next day or two). After 0.96, though, there will be some major, backwards-incompatible changes; several things, like the admin refactoring Jacob announced last night, will require changes that just can't be backwards-compatible, and will require a lot of activity on trunk for a while. In that light, Django 0.96 is important not just for getting all the cool features we've developed on trunk since 0.95, but also for being a relatively easy upgrade for users of 0.95 and a stable version to run with while we do a lot of work on trunk to get some things into their "ready for 1.0" state. It's not clear right now how long it'll be between 0.96 and the next release. In the meantime, 0.96 will serve as a pleasant mix of compatibility and new features; a couple of things have changed (like the location of the admin documentation views), but on the whole it should be an easy upgrade for anyone who's already at 0.95. If you've got any questions about all of this, feel free to reply and I'll do my best to answer them or delegate to someone who can. And if you've got some free time this week and want to help us kill bugs in the run up to 0.96, let us know and we'll be happy to show you how you can help. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---