On Nov 29, 10:33 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> 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?
Good choices, Adrian. I talked about this with you guys last sprint
(sorry by the way for missing this one) and I think these hit the
spot. Various branches may have to scramble a little to get up to date
but I think that will give them a better point of reference than "the
last time we branched". Also these are clearly backwards incompatible
- good to get those out of the way and make the upgrade path easier
for those starting with the next major version, and add the less-
incompatible changes later.
>
> And, finally, a bit of a controversial statement, but...
>
> I think we ought to call the release 2.0.
>
Well Rails is about to release 2.0... oops, did I say that out loud?!
Great stuff!
-rob
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
