On Fri, May 2, 2008 at 1:12 AM, Warren <[EMAIL PROTECTED]> wrote: > > It looks like someone else hit the same trivial bug I ran into and put > some considerable effort into writing a test case for it. > > However, progress on getting this fix included seems to have stalled > over 3 months ago. Perhaps it was just never marked "Ready for > checkin"?
The fact that the ticket isn't marked Ready for Checkin will be the biggest reason that this hasn't been committed. Please don't confuse this delay with lack of interest - obviously, we'd like to fix every problem in Django, but we are all volunteers, so we just don't always have the time or resources to address every ticket as quickly as we would like. The only thing you can do is occasionally try to draw attention to your ticket using a gentle nudge like this one. If you can point at a recurring theme of error reports/questions in django-users that would be fixed by applying your patch, you should find your ticket gets attention faster. 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-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
