p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Renamed the "Supported versions" label.

This commit is contained in:
Tim Graham 2018-01-31 10:12:51 -05:00
parent 8f14ed6c81
commit 4775dcb521
4 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/howto/upgrade-version.txt
View File

@ -8,7 +8,7 @@ version has several benefits:
* New features and improvements are added. * New features and improvements are added.
* Bugs are fixed. * Bugs are fixed.
* Older version of Django will eventually no longer receive security updates. * Older version of Django will eventually no longer receive security updates.
(see :ref:`backwards-compatibility-policy`). (see :ref:`supported-versions-policy`).
* Upgrading as each new Django release is available makes future upgrades less * Upgrading as each new Django release is available makes future upgrades less
painful by keeping your code base up to date. painful by keeping your code base up to date.

3
docs/internals/contributing/committing-code.txt
View File

@ -153,8 +153,7 @@ Django's Git repository:
commit. This goes a *long way* in helping everyone follow your changes. commit. This goes a *long way* in helping everyone follow your changes.
* Separate bug fixes from feature changes. Bugfixes may need to be backported * Separate bug fixes from feature changes. Bugfixes may need to be backported
to the stable branch, according to the :ref:`backwards-compatibility policy to the stable branch, according to :ref:`supported-versions-policy`.
<backwards-compatibility-policy>`.
* If your commit closes a ticket in the Django `ticket tracker`_, begin * If your commit closes a ticket in the Django `ticket tracker`_, begin
your commit message with the text "Fixed #xxxxx", where "xxxxx" is the your commit message with the text "Fixed #xxxxx", where "xxxxx" is the

2
docs/internals/release-process.txt
View File

@ -116,7 +116,7 @@ A more generic example:
LTS to LTS upgrades). LTS to LTS upgrades).
* Z.0: Drop deprecation shims added in Y.0 and Y.1. * Z.0: Drop deprecation shims added in Y.0 and Y.1.
.. _backwards-compatibility-policy: .. _supported-versions-policy:
Supported versions Supported versions
================== ==================

4
docs/intro/whatsnext.txt
View File

@ -215,8 +215,8 @@ We follow this policy:
* Documentation fixes and improvements may be backported to the last release * Documentation fixes and improvements may be backported to the last release
branch, at the discretion of the committer, however, once a version of branch, at the discretion of the committer, however, once a version of
Django is :ref:`no longer supported<backwards-compatibility-policy>`, that Django is :ref:`no longer supported<supported-versions-policy>`, that version
version of the docs won't get any further updates. of the docs won't get any further updates.
* The `main documentation Web page`_ includes links to documentation for * The `main documentation Web page`_ includes links to documentation for
previous versions. Be sure you are using the version of the docs previous versions. Be sure you are using the version of the docs