Weblog

Django 0.95.1 released

We've just rolled out Django 0.95.1, a new minor release of Django which includes fixes for several bugs discovered in the original 0.95 release; 0.95.1 includes:

  • A patch for a small security vulnerability in the script Django's internationalization system uses to compile translation files (changeset 4360 in the "0.95-bugfixes" branch).
  • A fix for a bug in Django's authentication middleware which could cause apparent "caching" of a logged-in user (changeset 4361).
  • A patch which disables debugging mode in the flup FastCGI package Django uses to launch its FastCGI server, which prevents tracebacks from bubbling up during production use (changeset 4363).

It's recommended that anyone using the official 0.95 release upgrade to 0.95.1 to get these fixes, or apply the patches from the changesets linked above.

Posted by James Bennett on January 21, 2007

Comments

Fredrik Sundqvist January 21, 2007 at 10:51 a.m.

Keep up the good work!

Umbrae January 21, 2007 at 1:02 p.m.

An upgrade tutorial for anyone using .95 would be good - also, don't forget to change the link on the home page and such to reflect the latest release.

Evdawg January 21, 2007 at 4:39 p.m.

Yes, an update tutorial would be good, in fact, how would I *properly* upgrade from 0.95 to the development version?

Brett Parker January 21, 2007 at 7:32 p.m.

The 0.95 -> 0.95.1 upgrade is really just security fixes, so you just use the 0.95 code you already had in the 0.95.1 environment.

For upgrades to the svn trunk (completely different beast to 0.95.1), the usual place to look for instructions is http://code.djangoproject.com/wiki/Ba... - that gets updated with anything that needs to be done to keep in line with new releases and a track of what's changed between the last release and trunk. Assume that minor releases (like 0.95.1) have none of the changes in that are documented in the "After 0.95" section, the point releases are just security fixes, and should not introduce changes to the way the code works.

(Or at least, that's my understanding of the situation, James maybe able to tell you otherwise)

James Bennett January 22, 2007 at 2:55 a.m.

As Brett pointed out, 0.95.1 is really a minor bugfix release to deal with a couple security issues; upgrading from 0.95 to 0.95.1 shouldn't require any changes to your own code.

Migrating to 0.95.1 from 0.91 or 0.90 is a different matter, of course; the "removing the magic" wiki page has detailed information on everything that changed between 0.91 and 0.95: http://code.djangoproject.com/wiki/Re...

Vernon January 22, 2007 at 3:14 p.m.

Could someone clarify if my understanding is incorrect: I'm running the development version from subversion, and regularly run "svn update" to get the latest code (on a side note, congrats to the developers for the stability of the developmental code, I definitely have no issues running it). They way I understand it is that the latest development version will have the latest bug and security fixes, and certainly any fixes in a numbered release. Therefore, I won't need to do anything other than "svn update". Is this correct?

Michael Radziej January 23, 2007 at 5:35 a.m.

Yes, svn update includes all security fixes.

Graham Todd January 29, 2007 at 2:04 p.m.

Great to see new django releases! Even 0.00.1 increments :)

Does this fix include those ever popular patches for user password creation (so folks don't have manually enter their own hashes)? Those features are so popular it'd be nice to roll them into an official release ;-)

Thanks to everyone involved in the release and keep up the great work.

Adrian Holovaty January 29, 2007 at 6:06 p.m.

Graham: No, this release doesn't include that. That improvement will be in our 0.96 release.

Bennet January 30, 2007 at 8:37 p.m.

Does anyone have a rough idea of when version 0.96 and 1.0 will be released?

Frankie Robertson January 31, 2007 at 7:41 a.m.

I'm pretty sure it's one of these "when it's ready things". The core devs won't let it take too long and you can help it go faster by triaging tickets. Either that or run the development version, which is generally better than waiting.

Comments are closed

To prevent spam, comments are no longer allowed after sixty days.