Yuri Baburov wrote: > For me, the process of developing Queryset refactoring totally went > out of control. And everyone says that "all will be outdated after > queryset refactoring release so we won't do anything now."
As mentioned by someone else in this thread, this is partly due to not wanting to waste time working on something that is about to be replaced. It's also partly courtesy to those working on the new feature to make the new code easier to merge. But if there is truly a show-stopper problem, it should be fixed, and if it's not being noticed in the ticket system then it should be brought up on this list. > Problems are also with development of newforms-admin branch, that > trunk is not working for half week now (without patch appeared later > and discussed in django-dev). > Also, please, core devs, your answer on this situation. > How do you see it? What do you do to improve it? All code that is not in a release is not guaranteed to be 100% working all the time, that's just part of code development. If there's a problem with a mature branch branch like newforms-admin or trunk, then I am sure that it will be discussed and fixed in a timely manner. I don't see an issue if a branch is broken for a week here and there, especially after the code frenzy that was last weekend. Gary --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
