On 8/16/07, Norman Harman <[EMAIL PROTECTED]> wrote: > > I'd like this to be fixed. I'd like to update the patch incorporating any > concerns the > list might have. I wouldn't like there to be someone else posting a similar > email as this > one in 6mo wondering why my patch was never applied.
And I'd like a pony. :-) The most obvious reason that the patch hasn't been applied is that it isn't listed as 'ready for checkin' . This means that the triage team either hasn't looked at it yet, or if they have, they thought that the patch wasn't right. The absence of any comments from the triage team suggests that the former is the case. However, more generally: keep in mind that the core developers are all _very_ busy, and more importantly, are _volunteers_. Our time is very much a limited resource. Complaining that we haven't fixed your pet bug doesn't improve the situation - because we have to spend some of our Django-time writing messages like this one. Also - keep in mind that if you have a patch that fixes the problem, you can apply that patch in your local installations. Yes, it's annoying that it isn't in the core distribution, but that doesn't mean you are completely hamstrung. 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 -~----------~----~----~----~------~----~------~--~---
