#12198: CSRF changes not noted on backwards incompatible page
------------------------------------+---------------------------------------
Reporter: shadfc | Owner: nobody
Status: closed | Milestone:
Component: Documentation | Version: 1.1
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by lukeplant):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
Which page are you referring to? BackwardsIncompatibleChanges is not the
place for that kind of thing — it clearly says "If you're already running
Django 1.0, you need not worry about anything on this page" at the top.
The only place we have for this kind of thing at the moment is release
notes. The beginnings of the release notes for 1.2 do include the CSRF
changes:
http://code.djangoproject.com/browser/django/trunk/docs/releases/1.2-alpha.txt
Perhaps we need another place for this kind of thing. It might be a
compilation of the "backwards incompatible" section of release notes or
something like that. I'm going to close this as INVALID, but suggest you
bring this up on django-dev. Perhaps the solution is to create a wiki
page with notes for people following trunk.
--
Ticket URL: <http://code.djangoproject.com/ticket/12198#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
