On Mon, Feb 1, 2010 at 11:18 AM, Christophe Pettus <x...@thebuild.com> wrote: > > On Jan 31, 2010, at 7:10 PM, Russell Keith-Magee wrote: >> >> However, as noted in [1], you don't need to post to django-dev just to >> tell us you uploaded a patch. > > OK, sorry for the noise. Since I had uploaded the patch on 11/6/09, I > wanted to make sure I hadn't missed a step in the review process.
The ticket hasn't received attention yet because of the focus of the development cycle. We've been working primarily on new features since October. The only bugs we have been paying attention to are those that are particularly annoying, embarrassing, or resulting from features that we have added recently. Looking at the ticket for #12180 specifically, there are two things missing that would reduce the likelihood of the patch being included in Django 1.2 final: 1) A test case (or a reasonable explanation of why a test case isn't necessary or possible) 2) The Milestone flag isn't set. If your ticket doesn't hit this query [1], then it probably won't ever hit anyone's radar for v1.2. [1] http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&group=component&milestone=1.2&order=priority Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
