On Sun, Nov 22, 2009 at 5:17 AM, Tim Chase <django.us...@tim.thechases.com> wrote: >> 2. Mess around with the Sphinx processor and make it display point >> release numbers but link to the minor release. > > A big -1 if documentation can only be built with a custom version > of Sphinx, making it harder for others to build docs. A -0 if > it's something in stock Sphinx that can be twiddled via > configuration/setup.
It sounds like there's a vague consensus around option 3 (having 1.1.2 release notes), but for the record - option 2 doesn't mean a custom compiled version of Sphinx. Sphinx allows you to add custom tags and processing instructions (see docs/_ext/djangodocs.py). Django uses these to provide most of the useful cross references and version tagging in the docs, including versionadded. 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=.
