[1.1.X] Fixed small error in deprecation policy.
Backport of r11652 git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.1.X@11653 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
1f0266bd18
commit
0ed09c8a73
|
@ -56,7 +56,7 @@ These releases will contain new features, improvements to existing features, and
|
||||||
such. A minor release may deprecate certain features from previous releases. If a
|
such. A minor release may deprecate certain features from previous releases. If a
|
||||||
feature in version ``A.B`` is deprecated, it will continue to work in version
|
feature in version ``A.B`` is deprecated, it will continue to work in version
|
||||||
``A.B+1``. In version ``A.B+2``, use of the feature will raise a
|
``A.B+1``. In version ``A.B+2``, use of the feature will raise a
|
||||||
``PendingDeprecationWarning`` but will continue to work. Version ``A.B+3`` will
|
``DeprecationWarning`` but will continue to work. Version ``A.B+3`` will
|
||||||
remove the feature entirely.
|
remove the feature entirely.
|
||||||
|
|
||||||
So, for example, if we decided to remove a function that existed in Django 1.0:
|
So, for example, if we decided to remove a function that existed in Django 1.0:
|
||||||
|
|
Loading…
Reference in New Issue