Hi I have been using it, and I have found a few bugs. Some posted some not. An example would be the limit_choices_to. But Luke fixed it almost stragith away.
There is also every changing landscape, just take a look at the commit log. http://code.djangoproject.com/log/ The point is to develop an application which will support a business requires at least two things I think: 1) All the features you expect should work. Ie it must be polished. the limit_choices_to is an example of small feature that got over looked in the MR changes originally. 2) Stability, you cant spend weeks developing stuff and then have one change to framework complelty change the landscape forcing you to recode some stuff. Its not that I need someone to ';bless' it, its that I want it stabilised, made whole and complete and new branch made to continue all the raidcal and experimental stuff. That said, MR is openly advertised as a development branch. So you cant expect the above. However I am not comfortable starting a project against the current 0.91 because I beleive some of the changes in MR are key. In fact MR branch syntax and features are what made choose Django over dozens of other frameworks. Which is why I mentioned above a stable release of it would be brillaint. But its shapipng up to be a really nice framework :-) C --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---
