great response from someone at the center of the django universe.

the django devs have said it over and over: django's release schedule isn't determined by an urge to increment version numbers, but to make sure things are ready for release and won't cause any backpedaling down the road. you don't publish a news article before the 'i's are crossed and the 't's are dotted, so why treat software the same way?

#2070 has been seemingly sitting around forever, but given the major changes that just happened with the queryset-refactor and whats going on with the newforms-admin branch and other major undertakings, some things can, in fact, be relegated to the back-burner. i can understand why people think its been sitting around for too long, but consider the priority of what else is on the stove before focusing on getting it out of the kitchen -- especially when the development trunk has such a fantastic track record of stability.