I've been using trunk for over 9mo for in production website http://storymash.com
During that time, there's been 2-3 times my unittests have failed after I've svn updated django. Each time was a fairly quick fix. API changes aren't hard bugs to track down and fix. The advantages of all the great stuff that has been added to trunk far outweigh the time spent. In fact, I've learned a bit about Django internals tracking down those failing unittests. My current employer, uses .96 or newforms-admin/trunk for several minor but still business critical and public facing portions of it's websites statesman.com and austin360.com with *no* problems(well no Django problems anyway ;). The .96 projects started before I arrived or else they would probably be trunk as well. I've been nothing but impressed with the diligence and abilities of Django developers and community to maintain multiple stable branches. Compare Django release discipline and record to other major frameworks. And your PHB's should be scared to use anything but Django. -- Norman J. Harman Jr. Senior Web Specialist, Austin American-Statesman ___________________________________________________________________________ You've got fun! Check out Austin360.com for all the entertainment info you need to live it up in the big city! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
