How to get Django
Django is available open-source under the BSD license. We recommend using the latest version of Python 3, but you can also use Python 2.7. See the FAQ for the Python versions supported by each version of Django. Here’s how to get it:
Option 1: Get the latest official version
pip install Django==1.8.5
Option 2: Get the alpha for 1.9
As part of the Django 1.9 development process, Django 1.9a1 is available. This release is only for users who want to try the new version and help identify remaining bugs before the 1.9 release. Please read the 1.9 release notes before using this package.
Install the alpha with pip:
pip install --pre django
Or if you have pip < 1.4:
pip install https://www.djangoproject.com/download/1.9a1/tarball/
Option 3: Get the latest development version
The latest and greatest Django version is the one that’s in our Git repository (our revision-control system). This is only for experienced users who want to try incoming changes and help identify bugs before an official release. Get it using this shell command, which requires Git:
git clone https://github.com/django/django.git
You can also download a gzipped tarball of the development version. This archive is updated every time we commit code.
After you get it
See the installation guide for further instructions. Make sure you read the documentation that corresponds to the version of Django you’ve just installed.
And be sure to sign up for the django-users mailing list, where other Django users and the Django developers themselves all hang out to help each other.
Feature releases (A.B, A.B+1, etc.) will happen roughly every eight months. These releases will contain new features, improvements to existing features, and such.
Patch releases (A.B.C, etc.) will be issued as needed, to fix bugs and/or security issues. These releases will be 100% compatible with the associated feature release, unless this is impossible for security reasons or to prevent data loss. So the answer to "should I upgrade to the latest patch release?” will always be "yes."
Certain feature releases will be designated as long-term support (LTS) releases. These releases will get security and data loss fixes applied for a guaranteed period of time, typically three years.
See the supported versions policy for detailed guidelines about what fixes will be backported.
|Release Series||Latest Release||End of mainstream support1||End of extended support2|
|1.8 LTS||1.8.5||December 2015||Until at least April 2018|
|1.7||1.7.10||April 1, 2015||December 2015|
|1.6||1.6.11||September 2, 2014||April 1, 2015|
|1.5||1.5.12||November 6, 2013||September 2, 2014|
|1.4 LTS||1.4.22||February 26, 2013||October 1, 2015|
|1.3||1.3.7||March 23, 2012||February 26, 2013|
Here's what the future roadmap looks like:
|Release Series||Release Date||End of mainstream support1||End of extended support2|
|1.9||December 2015||August 2016||April 2017|
|1.10||August 2016||April 2017||December 2017|
|1.11 LTS||April 2017||December 2017||Until at least April 2020|
|2.03||December 2017||August 2018||April 2019|
 Security fixes, data loss bugs, crashing bugs, major functionality
bugs in newly-introduced features, and regressions from older versions of Django.
 Security fixes and data loss bugs.
 Python 3 only.