innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

A final *final* clarification in the release notes. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@13274 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
James Bennett 2010-05-17 16:48:32 +00:00
parent d88d0ec336
commit c40b131ed5
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/releases/1.2.txt
View File

@ -366,13 +366,14 @@ Backwards-incompatible changes in 1.2
Wherever possible the new features above have been introduced in a
backwards-compatible manner per :ref:`our API stability policy
<misc-api-stability>` policy. This means that existing code which
worked with Django 1.1 will continue to work with Django 1.2; such
code will, however, begin issuing warnings (see below for details).
<misc-api-stability>` policy. This means that practically all existing
code which worked with Django 1.1 will continue to work with Django
1.2; such code will, however, begin issuing warnings (see below for
details).
However, a handful of features *have* changed in ways that, for some
users, will be backwards-incompatible. Those changes are detailed
below.
users, will be immediately backwards-incompatible. Those changes are
detailed below.
CSRF Protection
---------------