That's right: our policy (http://docs.djangoproject.com/en/dev/internals/contributing/#branch-policy http://docs.djangoproject.com/en/dev/internals/contributing

That's right: our policy (http://docs.djangoproject.com/en/dev/internals/contributing/#branch-policy http://docs.djangoproject.com/en/dev/internals/contributing/...) is that, whenever possible, trunk be kept stable. "People should be able to run production sites against the trunk at any time." This isn't hyperbole: I have sites in production that run against trunk and are updated very frequently. That said, like all software, Django has bugs. There's a handful (45 right now) left (http://code.djangoproject.com/query?status=!closed&component=!Translations&component=!Documentation&milestone=1.1 http://code.djangoproject.com/query?status=!closed&compo...) that are serious enough to prevent calling anything "final" right now.