Adrian Holovaty wrote: > Without further ado, here's my list: > > * newforms-admin > * queryset-refactor > * django.newforms becomes django.forms > * Model-level validation > * Change django.templatetags not to use __path__ hacking > * #3591 -- Make INSTALLED_APPS an instance, and each app an instance > * #5361 -- File storage refactoring > * #285 -- WSGI SCRIPT_NAME and PATH_INFO stuff > > What am I forgetting?
newforms in generic views and comments too. This isn't being taken care of in newforms admin is it? We also have the features page made before the last sprint: http://code.djangoproject.com/wiki/VersionOneFeatures On a related note, the maxlength argument is currently issuing a PendingDeprecationWarning. It was talked that we would change to DeprecationWarning before the next release, but I think it should die before <what do we call it>.0. Should we change to DeprecationWarning now and remove it before the release or just axe it all now? > And, finally, a bit of a controversial statement, but... > > I think we ought to call the release 2.0. "The birth of Django" 1.910 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 -~----------~----~----~----~------~----~------~--~---
