diff options
| author | James Bennett <ubernostrum@gmail.com> | 2010-05-17 16:48:32 +0000 |
|---|---|---|
| committer | James Bennett <ubernostrum@gmail.com> | 2010-05-17 16:48:32 +0000 |
| commit | c40b131ed5d84d2de4442af2110c7462293858df (patch) | |
| tree | ea1fbe270277c6555692c7122b4573ab9bb25831 | |
| parent | d88d0ec336767c8e44c7d2b59a0eb6d8cac98c6e (diff) | |
A final *final* clarification in the release notes.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@13274 bcc190cf-cafb-0310-a4f2-bffc1f526a37
| -rw-r--r-- | docs/releases/1.2.txt | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/releases/1.2.txt b/docs/releases/1.2.txt index 4e9a4c2c06..6d76538e18 100644 --- a/docs/releases/1.2.txt +++ b/docs/releases/1.2.txt @@ -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 --------------- |