From 0f12924eb565e17e6b71091c2b0acf1369be8f1c Mon Sep 17 00:00:00 2001
From: Tim Graham <timograham@gmail.com>
Date: Thu, 2 Jun 2016 11:41:49 -0400
Subject: [PATCH] [1.8.x] Updated release notes links to prevent warnings with
Sphinx 1.4.2.
Backport of 149ace94dfc10504a0e69462c7737f5ce05340a4 from master
---
docs/releases/1.0.txt | 2 +-
docs/releases/1.1.txt | 9 ++++-----
docs/releases/1.2.txt | 20 ++++++++++----------
docs/releases/1.3.txt | 28 +++++++++-------------------
docs/releases/1.4.txt | 24 ++++++++++++------------
docs/releases/1.5.txt | 24 ++++++++++++------------
docs/releases/1.6.txt | 19 ++++++++++---------
docs/releases/1.7.txt | 22 +++++++++++-----------
docs/releases/1.8.txt | 22 +++++++++++-----------
9 files changed, 80 insertions(+), 90 deletions(-)
diff --git a/docs/releases/1.0.txt b/docs/releases/1.0.txt
index 162caaa3a9..7cd0749cc9 100644
--- a/docs/releases/1.0.txt
+++ b/docs/releases/1.0.txt
@@ -22,7 +22,7 @@ contributions overtake those made privately.
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.
diff --git a/docs/releases/1.1.txt b/docs/releases/1.1.txt
index 38212615cc..f824dc0147 100644
--- a/docs/releases/1.1.txt
+++ b/docs/releases/1.1.txt
@@ -2,15 +2,12 @@
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:
@@ -175,6 +172,8 @@ be upgraded to a ``DeprecationWarning``, which will be displayed loudly. Django
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
========================
diff --git a/docs/releases/1.2.txt b/docs/releases/1.2.txt
index 368c436b39..2de5e06e8f 100644
--- a/docs/releases/1.2.txt
+++ b/docs/releases/1.2.txt
@@ -6,12 +6,10 @@ Django 1.2 release notes
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
========
@@ -115,6 +113,8 @@ A roadmap for Django's overall 2.x Python support, and eventual
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
========================
@@ -1073,10 +1073,10 @@ to provide localizers the possibility to translate date and time formats. They
were translatable :term:`translation strings <translation string>` that could
be recognized because they were all upper case (for example
:setting:`DATETIME_FORMAT`, :setting:`DATE_FORMAT`, :setting:`TIME_FORMAT`).
-They have been deprecated in favor of the new :ref:`Format localization
-<format-localization>` infrastructure that allows localizers to specify that
-information in a ``formats.py`` file in the corresponding
-``django/conf/locale/<locale name>/`` directory.
+They have been deprecated in favor of the new :doc:`/topics/i18n/formatting`
+infrastructure that allows localizers to specify that information in a
+``formats.py`` file in the corresponding ``django/conf/locale/<locale name>/``
+directory.
GeoDjango
---------
diff --git a/docs/releases/1.3.txt b/docs/releases/1.3.txt
index c8720e8524..ef69665e65 100644
--- a/docs/releases/1.3.txt
+++ b/docs/releases/1.3.txt
@@ -6,11 +6,11 @@ Django 1.3 release notes
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
========
@@ -28,27 +28,15 @@ new features from landing, including:
* 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`_.
+:ref:`begins the deprecation process for some features
+<deprecated-features-1.3>`.
-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.
-
-.. _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
====================
@@ -64,6 +52,8 @@ supported Python version will be 2.5. A document outlining our full
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
========================
diff --git a/docs/releases/1.4.txt b/docs/releases/1.4.txt
index 064f31e787..95d62b16b2 100644
--- a/docs/releases/1.4.txt
+++ b/docs/releases/1.4.txt
@@ -6,16 +6,12 @@ Django 1.4 release notes
Welcome to Django 1.4!
-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.3 or older versions. We've also dropped some
-features, which are detailed in :ref:`our deprecation plan
-<deprecation-removed-in-1.4>`, and we've `begun the deprecation process for
-some features`_.
-
-.. _`new features`: `What's new in Django 1.4`_
-.. _`backwards incompatible changes`: `Backwards incompatible changes in 1.4`_
-.. _`begun the deprecation process for some features`: `Features deprecated in 1.4`_
+These release notes cover the :ref:`new features <whats-new-1.4>`, as well as
+some :ref:`backwards incompatible changes <backwards-incompatible-1.4>` you'll
+want to be aware of when upgrading from Django 1.3 or older versions. We've
+also dropped some features, which are detailed in :ref:`our deprecation plan
+<deprecation-removed-in-1.4>`, and we've :ref:`begun the deprecation process
+for some features <deprecated-features-1.4>`.
Overview
========
@@ -56,8 +52,8 @@ Other notable new features in Django 1.4 include:
Wherever possible we try to introduce new features in a backwards-compatible
manner per :doc:`our API stability policy </misc/api-stability>` policy.
However, as with previous releases, Django 1.4 ships with some minor
-`backwards incompatible changes`_; people upgrading from previous versions
-of Django should read that list carefully.
+:ref:`backwards incompatible changes <backwards-incompatible-1.4>`; people
+upgrading from previous versions of Django should read that list carefully.
Python compatibility
====================
@@ -77,6 +73,8 @@ Django does not support Python 3.x at this time. At some point before the
release of Django 1.4, we plan to publish a document outlining our full
timeline for deprecating Python 2.x and moving to Python 3.x.
+.. _whats-new-1.4:
+
What's new in Django 1.4
========================
@@ -665,6 +663,8 @@ Django 1.4 also includes several smaller improvements worth noting:
useful in tests that don't need to hit a database. See
:ref:`testcase_hierarchy_diagram`.
+.. _backwards-incompatible-1.4:
+
Backwards incompatible changes in 1.4
=====================================
diff --git a/docs/releases/1.5.txt b/docs/releases/1.5.txt
index 498fa684a1..6ff6066866 100644
--- a/docs/releases/1.5.txt
+++ b/docs/releases/1.5.txt
@@ -6,16 +6,12 @@ Django 1.5 release notes
Welcome to Django 1.5!
-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.4 or older versions. We've also dropped some
-features, which are detailed in :ref:`our deprecation plan
-<deprecation-removed-in-1.5>`, and we've `begun the deprecation process for
-some features`_.
-
-.. _`new features`: `What's new in Django 1.5`_
-.. _`backwards incompatible changes`: `Backwards incompatible changes in 1.5`_
-.. _`begun the deprecation process for some features`: `Features deprecated in 1.5`_
+These release notes cover the :ref:`new features <whats-new-1.5>`, as well as
+some :ref:`backwards incompatible changes <backwards-incompatible-1.5>` you'll
+want to be aware of when upgrading from Django 1.4 or older versions. We've
+also dropped some features, which are detailed in :ref:`our deprecation plan
+<deprecation-removed-in-1.5>`, and we've :ref:`begun the deprecation process
+for some features <deprecated-features-1.5>`.
Overview
========
@@ -51,8 +47,8 @@ Other notable new features in Django 1.5 include:
Wherever possible we try to introduce new features in a backwards-compatible
manner per :doc:`our API stability policy </misc/api-stability>`.
However, as with previous releases, Django 1.5 ships with some minor
-`backwards incompatible changes`_; people upgrading from previous versions
-of Django should read that list carefully.
+:ref:`backwards incompatible changes <backwards-incompatible-1.5>`; people
+upgrading from previous versions of Django should read that list carefully.
One deprecated feature worth noting is the shift to "new-style" :ttag:`url` tag.
Prior to Django 1.3, syntax like ``{% url myview %}`` was interpreted
@@ -118,6 +114,8 @@ to start porting now.
We plan to offer first-class, production-ready support for Python 3 in our next
release, Django 1.6.
+.. _whats-new-1.5:
+
What's new in Django 1.5
========================
@@ -348,6 +346,8 @@ Django 1.5 also includes several smaller improvements worth noting:
* The admin's list filters can now be customized per-request thanks to the new
:meth:`django.contrib.admin.ModelAdmin.get_list_filter` method.
+.. _backwards-incompatible-1.5:
+
Backwards incompatible changes in 1.5
=====================================
diff --git a/docs/releases/1.6.txt b/docs/releases/1.6.txt
index dddf47df90..873584e1b4 100644
--- a/docs/releases/1.6.txt
+++ b/docs/releases/1.6.txt
@@ -24,15 +24,12 @@
Welcome to Django 1.6!
-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.5 or older versions. We've also dropped some features, which are detailed in
-:ref:`our deprecation plan <deprecation-removed-in-1.6>`, and we've `begun the
-deprecation process for some features`_.
-
-.. _`new features`: `What's new in Django 1.6`_
-.. _`backwards incompatible changes`: `Backwards incompatible changes in 1.6`_
-.. _`begun the deprecation process for some features`: `Features deprecated in 1.6`_
+These release notes cover the :ref:`new features <whats-new-1.6>`, as well as
+some :ref:`backwards incompatible changes <backwards-incompatible-1.6>` you'll
+want to be aware of when upgrading from Django 1.5 or older versions. We've
+also dropped some features, which are detailed in :ref:`our deprecation plan
+<deprecation-removed-in-1.6>`, and we've :ref:`begun the deprecation process
+for some features <deprecated-features-1.6>`.
Python compatibility
====================
@@ -46,6 +43,8 @@ with Django 1.7, the minimum supported Python version will be 2.7.
Python 3.4 is not supported, but support will be added in Django 1.7.
+.. _whats-new-1.6:
+
What's new in Django 1.6
========================
@@ -370,6 +369,8 @@ Minor features
default value. Passwords :ref:`will be upgraded <password-upgrades>` to use
the new iteration count as necessary.
+.. _backwards-incompatible-1.6:
+
Backwards incompatible changes in 1.6
=====================================
diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt
index 63eef9e51a..7db465eed5 100644
--- a/docs/releases/1.7.txt
+++ b/docs/releases/1.7.txt
@@ -6,16 +6,12 @@ Django 1.7 release notes
Welcome to Django 1.7!
-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.6 or older versions. We've `begun the deprecation process for some features`_,
-and some features have reached the end of their deprecation process and
-`have been removed`_.
-
-.. _`new features`: `What's new in Django 1.7`_
-.. _`backwards incompatible changes`: `Backwards incompatible changes in 1.7`_
-.. _`begun the deprecation process for some features`: `Features deprecated in 1.7`_
-.. _`have been removed`: `Features removed in 1.7`_
+These release notes cover the :ref:`new features <whats-new-1.7>`, as well as
+some :ref:`backwards incompatible changes <backwards-incompatible-1.7>` you'll
+want to be aware of when upgrading from Django 1.6 or older versions. We've
+:ref:`begun the deprecation process for some features
+<deprecated-features-1.7>`, and some features have reached the end of their
+deprecation process and :ref:`have been removed <removed-features-1.7>`.
Python compatibility
====================
@@ -33,6 +29,8 @@ Django 1.6 until you can upgrade your Python version. Per :doc:`our support
policy </internals/release-process>`, Django 1.6 will continue to receive
security support until the release of Django 1.8.
+.. _whats-new-1.7:
+
What's new in Django 1.7
========================
@@ -944,6 +942,8 @@ Validators
* :func:`~django.core.validators.validate_email` now accepts addresses with
IPv6 literals, like ``example@[2001:db8::1]``, as specified in RFC 5321.
+.. _backwards-incompatible-1.7:
+
Backwards incompatible changes in 1.7
=====================================
@@ -1810,7 +1810,7 @@ Private APIs ``django.db.models.sql.where.WhereNode.make_atom()`` and
``django.db.models.sql.where.Constraint`` are deprecated in favor of the new
:doc:`custom lookups API </ref/models/lookups>`.
-.. removed-features-1.7:
+.. _removed-features-1.7:
Features removed in 1.7
=======================
diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt
index 803300e9d7..7aba611155 100644
--- a/docs/releases/1.8.txt
+++ b/docs/releases/1.8.txt
@@ -6,22 +6,18 @@ Django 1.8 release notes
Welcome to Django 1.8!
-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.7 or older versions. We've also `begun the deprecation process for some
-features`_, and some features have reached the end of their deprecation process
-and `have been removed`_.
+These release notes cover the :ref:`new features <whats-new-1.8>`, as well as
+some :ref:`backwards incompatible changes <backwards-incompatible-1.8>` you'll
+want to be aware of when upgrading from Django 1.7 or older versions. We've
+also :ref:`begun the deprecation process for some features
+<deprecated-features-1.8>`, and some features have reached the end of their
+deprecation process and :ref:`have been removed <removed-features-1.8>`.
Django 1.8 has been designated as Django's second :ref:`"Long-Term Support"
(LTS) <lts-releases>` release. It will receive security updates for at least
three years after its release. Support for the previous LTS, Django 1.4, will
end 6 months from the release date of Django 1.8.
-.. _`new features`: `What's new in Django 1.8`_
-.. _`backwards incompatible changes`: `Backwards incompatible changes in 1.8`_
-.. _`begun the deprecation process for some features`: `Features deprecated in 1.8`_
-.. _`have been removed`: `Features removed in 1.8`_
-
Python compatibility
====================
@@ -33,6 +29,8 @@ Django 1.8 is the first release to support Python 3.5.
Due to the end of upstream support for Python 3.2 in February 2016, we won't
test Django 1.8.x on Python 3.2 after the end of 2016.
+.. _whats-new-1.8:
+
What's new in Django 1.8
========================
@@ -662,6 +660,8 @@ Validators
* :class:`~django.core.validators.URLValidator` now supports IPv6 addresses,
unicode domains, and URLs containing authentication data.
+.. _backwards-incompatible-1.8:
+
Backwards incompatible changes in 1.8
=====================================
@@ -1724,7 +1724,7 @@ After switching to the new signature the router will also be called by the
:class:`~django.db.migrations.operations.RunPython` and
:class:`~django.db.migrations.operations.RunSQL` operations.
-.. removed-features-1.8:
+.. _removed-features-1.8:
Features removed in 1.8
=======================