Django 1.4 release candidate 2 issued
As part of the updated Django 1.4 release process, today we've issued Django 1.4 release candidate 2, which will hopefully be the final pre-release package before Django 1.4.
Because this is a pre-release package, it is of course not recommended for production use, but if you'd like to try it out in a safe environment and help spot any remaining bugs before 1.4 final, feel free to grab a copy and give it a spin.
You can get a copy of the 1.4 release candidate from our downloads page, and we recommend you read the release notes. The most important note there is that Django 1.4 drops support for Python 2.4; to run the release candidate you'll need at least Python 2.5. Also, for the security conscious, signed MD5 and SHA1 checksums of the 1.4 release candidate package are available.
If you spot serious bugs that could block the release of Django 1.4, please head over to our Trac instance, look to see if a ticket has already been filed, and if not open a new one.
At present, two bugs are known which will be fixed prior to release, but which are minor enough that we've felt issuing this release candidate is appropriate. Those are tracked by tickets 17758 and 17838.
If no show-stopping bugs are reported within the next seven days, we'll move ahead and issue the Django 1.4 release next week.
Posted by James Bennett on March 14, 2012