Agreed the reasoning is sound. This is a major bug as far as I'm concerned and I'd like to see it backported. Thanks for bringing it up.
Marc On 6 Dec 2015 1:05 p.m., "Shai Berger" <s...@platonix.com> wrote: > On Sunday 06 December 2015 14:52:08 Aymeric Augustin wrote: > > > On 6 déc. 2015, at 10:49, James Bennett <ubernost...@gmail.com> wrote: > > > > > > Thoughts? > > > > I don’t think anyone ever prevented a core dev who wanted to backport a > > commit from doing so — unless it carried a risk of backwards > > incompatibility, which doesn’t appear to be the case here. > > Not to my knowledge also, but we did have a policy change, about two years > ago, against arbitrary backports at a core-dev's judgment (which was the > norm > until then). So, I find it very proper that James has brought this up on > the > list. > > That said, the reasoning for backporting seems sound to me, so +1. > > Shai. > -- 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/CAMwjO1F949HA_pZis54b7S55ZKbdUTLcdEMefOx2wa%2Bx3_dqwA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
