Just take the current revision, it is as stable as any other revision(probably moreso), I would stick to that, and track the trunk and if a new feature comes out that you want, review the backwards incompatible changes page, and then SVN up.
On Apr 2, 12:02 pm, SteveMc <[EMAIL PROTECTED]> wrote: > On this topic, our company's moving over to Python and Django. A lot > of our developers are understandably wary of using trunk code, but > there are a lot of features we'd like that aren't in 0.96. Does anyone > have any advice on a trunk revision to stick with that's stable and > includes most of the big changes from 0.96? We would rather choose a > revision and stick with it rather than taking the risk of being on the > bleeding edge. The most important features we'd like are the unicode > support and to reduce the API changes when the next release is made. > > Thanks, > > Steve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
