Just a quick procedural thing: The 0.96.2 tarball created for the recent security fix was generated from the 0.96 setup.py script, which gets you the Django source tree but misses things like the documentation files that we distribute with Django. This has caused a couple of issues with downstream distribution, since maintainers had to go and fetch those files manually for packaging.
The setup.py in trunk (verified just a moment ago) gets things right and includes, as far as I can tell, everything that ought to be included, but I'm wary of trying to backport stuff from it into a release branch that's really only supposed to get security fixes. As an alternative, I can generate a complete tarball pretty easily from an 'svn export' of the 0.96-bugfixes branch, and that seems to me to be the best thing to do now (which would simply replace the 0.96.2 tarball with one that, while identical code-wise, contains the additional files) and for the future (e.g., if we have another security fix to push out during the support period for the 0.96 line. Anyone have strong objections to doing this? -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
