On Sat, Nov 21, 2009 at 9:59 PM, Luke Plant <l.plant...@cantab.net> wrote: > On Saturday 21 November 2009 11:54:40 Tim Chase wrote: > 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.
This would be a break in tradition. We don't (or haven't in the past) done release notes for point releases, as they are normally only bugfixes and/or security updates. I can see three possiblities here: 1. Mark the feature as 'versionadded:1.2" in trunk; in the 1.1.X branch, mark it 'versionadded:1.1', but with an explanatory note clarifying that strictly, it's 1.1.2. 2. Mess around with the Sphinx processor and make it display point release numbers but link to the minor release. 3. Actually create a 1.1.2 release notes document, whose sole purpose is to document this extraordinary feature. I don't have any preference on the color of this particular bikeshed. If pressed, I'd probably say option 3. Regarding the issue of whether this is the only reference failure in the docs - there is actually one other; the 1.2 release notes aren't listed in the release notes index file. Yours, Russ Magee %-) -- 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=.
