On Mar 27, 2012 8:45 AM, "Hanne Moa" <hanne....@gmail.com> wrote: > > Let's just do it. Let's not wait for a generic migration tool! I'd > rather the energy was spent on the app-refactor *now*, and fixing the > email-fields *now*, which would remove some of the pressure on fixing > the Identity/Authentication/Authorization architecture. >
There's still several months before the 1.5 feature freeze. It's not out of the realm of possibility that some of these summer projects will land in 1.5. Given that, I'd rather do it right. Proper standards support for the email field is important, arguably a 1.5 release blocker, but so long as there is a good chance that migration support will be 1.5's poster-child feature then I think email support should be our poster child's poster child. Best, Alex Ogier -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
