Hi there, On Tue, Oct 7, 2008 at 1:17 PM, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > You can't put anything with spaces in there. It feels a little > inconsistent to put 1.1 in there, since we generally hold off talking > about version numbers from the future so that bug reporters are forced > to use accurate version numbers. > > I'd probably say that we bite the bullet and use 1.1 except then we > should do what one of the Spanish Marc's has suggested in a ticket > somewhere (could I be any less specific on the details, do you think?) > and make the main documentation link point to the 1.0 docs and put a > "development docs this way" sign up somewhere.
That's me! There are two consecutive tickets that talk about version[added|changed]. You may be talking about #8992 and there's also #8991 (about when to remove those strings :P) >From my POV, when you commit something to trunk you know it's going to be in the next X.Y release, so it's safe to put the X.Y version "to-be-released-next". I don't really think people need to know in which exact moment of the development process the feature went in (if you are tracking trunk, you *track* it). *Maybe* we could instruct Sphinx in ways to change the X.Y thing "automagically" to "Development Version" when X.Y refers to the yet-to-be-released version. But writting there anything that is not the X.Y of the next version means more work *before release* (change whatever was there to the corresponding X.Y). Just my 0.02, Marc --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
