On 1 May 2013, at 00:13, Donald Stufft <[email protected]> wrote: > > On Apr 30, 2013, at 7:10 PM, Andrew Ingram <[email protected]> wrote: > >> On 30 Apr 2013, at 23:38, Shai Berger <[email protected]> wrote: >>> I see one issue with this: According to current procedures, if this >>> timeline >>> is followed, support for 1.4 will be dropped less than 6 months after the >>> release of 1.5. At least for some of us (which, as I mentioned earlier on >>> the >>> list, only moved to 1.4 when the 1.5 release forced us to), this may be a >>> bit >>> of a problem. >>> >>> Shai. >> >> It seems like 1.4 support might need to be extended. I'm assuming that given >> the success of the kickstarter campaign, Andrew's schema migration >> functionality will be made available to 1.4, and the functionality seems to >> be a prerequisite for migrating to the new way of handling user models. >> >> Andy > > There is no requirement to migrate for the new way to handle user models. The > only time you'd need to migrate is if you want to swap out your existing user > models that Django provides with new ones. If you don't do that then you > don't need to migrate.
Absolutely, there's no requirement to migrate, but it does have the feel of an weird kind of deprecation. Obviously there are workarounds, like you said, I can upgrade to 1.5 without changing user models (though that does involve incurring a bit of technical debt). Anyway, this whole line of reasoning was based on the faulty belief that Andrew's work will be added to 1.4, rather than as an external tool, so never mind! Andy -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
