On Tue, 2008-10-07 at 07:38 -0500, Tim Chase wrote: > > I'm still coming to grips with Sphinx, but is there any reason that we > > can't just use 1.X or 1.SVN as a version number for the development > > version? That gets around the need to specify the exact version > > number, but keeps it reasonably obvious that it's a development > > version. > > If non-digits are allowed, one might even consider something like > > trunk.8123 > > to indicate that the documentation was added for a feature in > trunk, r8123 which would help pair documentation with code > sitting on a developer's machine.
Please, no. The idea isn't to create even more work for us. :-) This would mean we can't commit correct documentation with the change that introduces a feature (since one needs to know the revision number) and you end up having to always remember to make a second commit. If a developer is tracking trunk they can keep up to speed themselves. If they can't, there's a 1.0.X branch there for their very own personal use. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
