Clarify number of deprecations in the beta release.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@12395 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
James Bennett 2010-02-06 20:48:55 +00:00
parent ae9866663c
commit d334713ea2
1 changed files with 9 additions and 9 deletions

View File

@ -26,15 +26,15 @@ updated features in Django between 1.1 and 1.2 alpha.
Deprecations and other changes in 1.2 beta
==========================================
This beta release deprecates one portion of public API, and introduces
a potentially backwards-incompatible change to another. Under
:ref:`our API stability policy <misc-api-stability>`, deprecation
proceeds over multiple release cycles: initially, the deprecated API
will raise ``PendingDeprecationWarning``, followed by raising
``DeprecationWarning`` in the next release, and finally removal of the
deprecated API in the release after that. APIs beginning the
deprecation process in Django 1.2 will be removed in the Django 1.4
release.
This beta release deprecates two portions of public API, and
introduces a potentially backwards-incompatible change to
another. Under :ref:`our API stability policy <misc-api-stability>`,
deprecation proceeds over multiple release cycles: initially, the
deprecated API will raise ``PendingDeprecationWarning``, followed by
raising ``DeprecationWarning`` in the next release, and finally
removal of the deprecated API in the release after that. APIs
beginning the deprecation process in Django 1.2 will be removed in the
Django 1.4 release.
Unit test runners