Will do, thanks. If we haven't gotten the go-ahead before the 22nd I'll un-assign it before I go on vacation.
On Tuesday, December 16, 2014 6:58:08 AM UTC-7, Markus Holtermann wrote: > > Hi Mike, > > Thanks for grabbing it. I'd suggest to wait for the patch for #23983 being > merged and than work on the updated master branch. From my point of view, > the pull-request shouldn't add this new feature, as it would be backported > to 1.7 which isn't covered by the backporting guidelines. Thus it'd be a > new feature in 1.8 > > I would also wait for a +1 from a core dev or the technical board to start > working on it. > > /Markus > > On Tuesday, December 16, 2014 2:17:42 PM UTC+1, mha...@ualberta.ca wrote: >> >> Hello all, >> >> I just grabbed this ticket, but then I noticed in pull request #3735 that >> we don't have a consensus as to whether this feature should be added. Since >> I'm new around here, I'd like to ask everyone's opinion on whether we >> should move forward on this. I can implement it within a few days, and it >> would give me a good chance to poke around the migrations framework (last >> time I used Django, migrations were still handled by South). >> >> Thanks, >> Mike >> > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/4ba9b519-6a7a-4161-8349-ddafe352178b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
