On Saturday 21 November 2009 11:54:40 Tim Chase wrote: > Just noticed this in [1] > > -------------------------------------- > csrf_tokenś > > New in Django 1.1.2: > > System Message: WARNING/2 > (/home/djangodocs/en/dev/ref/templates/builtins.txt) > > undefined label: releases-1.1.2 > -------------------------------------- > > > Looks like some tag/label needs to be created for the doc build > process to find it. If this needs a bug report to be filed, I > can do that too, but it may just be a fast "whoops" fix. I'm > guessing it's not the only instance in the docs, but I'd also > guess that the same fix should solve all of them.
It is supposed to be 1.1.2, and at the moment it is the only instance in the docs. The circumstances which created the need for this are rare — we added a new 'feature' to the 1.1 branch, which in reality is a no-op, but will help to ease the transition from the 1.1.X branch to the 1.2.X branch. There is a comment on this bug: http://code.djangoproject.com/ticket/12130#comment:6 The problem is there are no 1.1.2 release notes yet. Also, if you put "versionchanged:: 1.2", our docs are set up to parse that as referring to the next version of Django, so it says "Development version". The same isn't true of 1.1.2. I don't know how this should be handled. Perhaps the easiest way is to start the tentative 1.1.2 release notes as has been done with the 1.2 notes. Luke -- "DO NOT DISTURB. I'm disturbed enough already." Luke Plant || http://lukeplant.me.uk/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=.
