diff options
| author | Luke Plant <L.Plant.98@cantab.net> | 2009-10-24 14:10:00 +0000 |
|---|---|---|
| committer | Luke Plant <L.Plant.98@cantab.net> | 2009-10-24 14:10:00 +0000 |
| commit | 92090253fe743830e9391095f552af0724a40ca7 (patch) | |
| tree | a7a1d6700aa7c2e869de7da7cba72ceeb5d2801c | |
| parent | a02a6fab66afc9462c79cc4914f4624b640165f4 (diff) | |
Fixed small error in deprecation policy.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@11652 bcc190cf-cafb-0310-a4f2-bffc1f526a37
| -rw-r--r-- | docs/internals/release-process.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/internals/release-process.txt b/docs/internals/release-process.txt index 6d4ad9e8c9..e990ab8ab6 100644 --- a/docs/internals/release-process.txt +++ b/docs/internals/release-process.txt @@ -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 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 -``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. So, for example, if we decided to remove a function that existed in Django 1.0: |