Kaydet (Commit) d334713e authored tarafından James Bennett's avatar James Bennett

Clarify number of deprecations in the beta release.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@12395 bcc190cf-cafb-0310-a4f2-bffc1f526a37
üst ae986666
...@@ -26,15 +26,15 @@ updated features in Django between 1.1 and 1.2 alpha. ...@@ -26,15 +26,15 @@ updated features in Django between 1.1 and 1.2 alpha.
Deprecations and other changes in 1.2 beta Deprecations and other changes in 1.2 beta
========================================== ==========================================
This beta release deprecates one portion of public API, and introduces This beta release deprecates two portions of public API, and
a potentially backwards-incompatible change to another. Under introduces a potentially backwards-incompatible change to
:ref:`our API stability policy <misc-api-stability>`, deprecation another. Under :ref:`our API stability policy <misc-api-stability>`,
proceeds over multiple release cycles: initially, the deprecated API deprecation proceeds over multiple release cycles: initially, the
will raise ``PendingDeprecationWarning``, followed by raising deprecated API will raise ``PendingDeprecationWarning``, followed by
``DeprecationWarning`` in the next release, and finally removal of the raising ``DeprecationWarning`` in the next release, and finally
deprecated API in the release after that. APIs beginning the removal of the deprecated API in the release after that. APIs
deprecation process in Django 1.2 will be removed in the Django 1.4 beginning the deprecation process in Django 1.2 will be removed in the
release. Django 1.4 release.
Unit test runners Unit test runners
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment