Hi guys, I've been wondering of late if we need to cut a new release. I have a few reasons:
1) Its been six months since the release of 0.96, and we've made some good progress since then; 2) The current trunk seems to be in pretty good condition, and Malcolm is about to land a big refactor of query.py which could lead to some temporary instability; 3) Malcolm has hinted that he has a stash of backwards incompatible changes that he has been queuing up to make in one big hit prior to a release (If I have misunderstood you here, Malcolm, I apologise) However, most importantly: 4) The max_length issue is starting to get ridiculous. So far, the running ticket count is: 5254, 5252, 5240, 5210, 5208, 5194, 5184, 5162, 5159, 5144, 5119, 5117. For every user that has gone to the trouble to post a ticket, there is probably a whole lot more that have tried, failed, and said "Perfectionists with deadlines? Rubbish! Can't even get their tutorials right!" Newforms-admin is still a little bit off being able to land, so the previously announced schedule for the deprecation of oldforms would probably need to be pushed back by a release. However I don't see any other way to kill the max_length problem. One the one hand, the max_length problem is is an RTFM issue - but on the other hand, if multiple users keep making the the same error over and over again, there comes a point at which you have to question whether the documentation is really the problem. Comments? Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
