On Fri, 2008-12-05 at 03:17 -0600, James Bennett wrote: > On Fri, Dec 5, 2008 at 2:07 AM, Florian Lindner <[EMAIL PROTECTED]> wrote: > > Last time I used Django (pre 1.0) it was recommended to always use > > trunk since the last released version was too outdated. Has this > > changed? > > Yes. > > 0.96 -> 1.0 involved a large number of backwards-incompatible changes, > so many people simply followed trunk so that they could make changes > as they went rather than having a single huge upgrade process. > > From 1.0 on, this is not a problem because compatibility is preserved > between releases. Thus, your best bet (unless you're a developer > actively working on Django itself, and interested in helping to > develop new features or fix new bugs) is simply to use the latest > release (Django 1.0.2).
That being said, we (the maintainers) have also agreed that we aren't going to destabilise trunk in any cavalier fashion. Following trunk should be no more risky than it was pre-1.0, but it might not be as necessary. It will probably be less work than before 1.0, since there won't be all the backwards incompatible changes (at least in the areas marked in our API stability document) to worry about. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
