From c40b131ed5d84d2de4442af2110c7462293858df Mon Sep 17 00:00:00 2001 From: James Bennett Date: Mon, 17 May 2010 16:48:32 +0000 Subject: [PATCH] A final *final* clarification in the release notes. git-svn-id: http://code.djangoproject.com/svn/django/trunk@13274 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/releases/1.2.txt | 11 ++++++----- 1 file 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 -` 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). +` 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 ---------------