Django 1.7 released
After nearly a year of development, today we're proud to announce the release of Django 1.7.
As always, the release notes cover everything in-depth, but some of the major highlights of Django 1.7 are:
- A new built-in database migration system. Notes on upgrading from South (a popular third-party application providing migration functionality) are also available.
- A refactored concept of Django applications. Django applications are no longer tied to the existence of a models files, and can now specify both configuration data and code to be executed as Django starts up.
- Improvements to the model Field API to support migrations and, in the future, to enable easy addition of composite-key support to Django's ORM.
- Improvements for custom Manager and QuerySet classes, allowing reverse relationship traversal to specify the Manager to use, and creation of a Manager from a custom QuerySet class.
- An extensible system check framework which can assist developers in detecting and diagnosing errors.
And that's just the tip of the iceberg; Django 1.7 is jam-packed with useful new features and functionality, and they're all covered in the 1.7 release notes.
Alongside Django 1.7, today we are issuing bugfix releases in the 1.4, 1.5 and 1.6 series, which correct some bugs which existed after the most recent security releases.
Today's releases are:
- Django 1.4.15 (download 1.4.15 | 1.4.15 checksums)
- Django 1.5.10 (download 1.5.10 | 1.5.10 checksums)
- Django 1.6.7 (download 1.6.7 | 1.6.7 checksums)
Also, with the release of Django 1.7, Django 1.5 has reached end-of-life. As such, Django 1.5.10 is the final release of the 1.5 series. Django 1.6 will continue to receive support until the release of Django 1.8. Django 1.4 is a long-term support release, and will be supported until at least March of 2015.