[1.10.x] Updated release notes links to prevent warnings with Sphinx 1.4.2.

Stability and forwards-compatibility

====================================

:doc:`The release of Django 1.0 </releases/1.0>` comes with a promise of API

The release of Django 1.0 comes with a promise of API

stability and forwards-compatibility. In a nutshell, this means that code you

develop against Django 1.0 will continue to work against 1.1 unchanged, and you

should need to make only minor changes for any 1.X release.

Django 1.1 release notes

========================

July 29, 2009

Welcome to Django 1.1!

Django 1.1 includes a number of nifty `new features`_, lots of bug

fixes, and an easy upgrade path from Django 1.0.

.. _new features: `What's new in Django 1.1`_

Django 1.1 includes a number of nifty :ref:`new features <whats-new-1.1>`, lots

of bug fixes, and an easy upgrade path from Django 1.0.

.. _backwards-incompatible-changes-1.1:

For more details on our deprecation policies and strategy, see

:doc:`/internals/release-process`.

.. _whats-new-1.1:

What's new in Django 1.1

========================

Welcome to Django 1.10!

These release notes cover the `new features`_, as well as some `backwards

incompatible changes`_ you'll want to be aware of when upgrading from Django

1.9 or older versions. We've :ref:`dropped some features<removed-features-1.10>`

that have reached the end of their deprecation cycle, and we've `begun the

deprecation process for some features`_.

.. _`new features`: `What's new in Django 1.10`_

.. _`backwards incompatible changes`: `Backwards incompatible changes in 1.10`_

.. _`dropped some features`: `Features removed in 1.10`_

.. _`begun the deprecation process for some features`: `Features deprecated in 1.10`_

These release notes cover the :ref:`new features <whats-new-1.10>`, as well as

some :ref:`backwards incompatible changes <backwards-incompatible-1.10>` you'll

want to be aware of when upgrading from Django 1.9 or older versions. We've

:ref:`dropped some features <removed-features-1.10>` that have reached the end

of their deprecation cycle, and we've :ref:`begun the deprecation process for

some features <deprecated-features-1.10>`.

Python compatibility

====================

Like Django 1.9, Django 1.10 requires Python 2.7, 3.4, or 3.5. We **highly

recommend** and only officially support the latest release of each series.

.. _whats-new-1.10:

What's new in Django 1.10

=========================

  ``allow_negative`` boolean parameter, defaulting to ``False``, to allow

  negative integers.

.. _backwards-incompatible-1.10:

Backwards incompatible changes in 1.10

======================================

Welcome to Django 1.2!

Nearly a year in the making, Django 1.2 packs an impressive list of `new

features`_ and lots of bug fixes. These release notes cover the new features,

as well as important changes you'll want to be aware of when upgrading from

Django 1.1 or older versions.

.. _new features: `What's new in Django 1.2`_

Nearly a year in the making, Django 1.2 packs an impressive list of :ref:`new

features <whats-new-1.2>` and lots of bug fixes. These release notes cover

the new features, as well as important changes you'll want to be aware of when

upgrading from Django 1.1 or older versions.

Overview

========

transition to Python 3.x, is currently being developed, and will be

announced prior to the release of Django 1.3.

.. _whats-new-1.2:

What's new in Django 1.2

========================

Welcome to Django 1.3!

Nearly a year in the making, Django 1.3 includes quite a few `new

features`_ and plenty of bug fixes and improvements to existing

features. These release notes cover the new features in 1.3, as well

as some `backwards-incompatible changes`_ you'll want to be aware of

when upgrading from Django 1.2 or older versions.

Nearly a year in the making, Django 1.3 includes quite a few :ref:`new features

<whats-new-1.3>` and plenty of bug fixes and improvements to existing features.

These release notes cover the new features in 1.3, as well as some

:ref:`backwards-incompatible changes <backwards-incompatible-changes-1.3>`

you'll want to be aware of when upgrading from Django 1.2 or older versions.

Overview

========

* Django's testing framework now supports (and ships with a copy of)

  `the unittest2 library`_.

There's plenty more, of course; see the coverage of `new features`_

below for a full rundown and details.

Wherever possible, of course, new features are introduced in a

backwards-compatible manner per :doc:`our API stability policy

</misc/api-stability>` policy. As a result of this policy, Django 1.3

`begins the deprecation process for some features`_.

Some changes, unfortunately, are genuinely backwards-incompatible; in

most cases these are due to security issues or bugs which simply

couldn't be fixed any other way. Django 1.3 includes a few of these,

and descriptions of them -- along with the (minor) modifications

you'll need to make to handle them -- are documented in the list of

`backwards-incompatible changes`_ below.

:ref:`begins the deprecation process for some features

<deprecated-features-1.3>`.

.. _new features: `What's new in Django 1.3`_

.. _backwards-incompatible changes: backwards-incompatible-changes-1.3_

.. _using Python's logging facilities: `Logging`_

.. _easy handling of static files: `Extended static files handling`_

.. _the unittest2 library: `unittest2 support`_

.. _begins the deprecation process for some features: `deprecated-features-1.3`_

Python compatibility

====================

timeline for deprecating Python 2.x and moving to Python 3.x will be

published shortly after the release of Django 1.3.

.. _whats-new-1.3:

What's new in Django 1.3

========================