On 12/6/06, Lakin Wecker <[EMAIL PROTECTED]> wrote: > I am also interested in helping with this situation. I've run into quite a > few patches that are reportedly working for some people. How do we help > get these triaged?
Yes, there are 175 active tickets with patches in the database. However, many (if not most) of these tickets don't make it easy to apply the patch provided. A well triaged patch has the following characteristics: - A clear, consise description of the problem - A clear, concise set of conditions and instructions for consistently replicating the problem - A brief discussion of the merits of any alternatives for fixing the problem - A patch that meets Django's coding guidelines - If the patch is non-trivial [1], evidence that there has been discussion on django-developers on the alternatives. - A regression test to prevent the problem in the future If any of these are missing, it means that I have to pick up the slack. While I would love to be able to stand up and say "Django has no known bugs", if I'm faced with an incomplete, possibly incorrect bug report (with or without a patch) in an area of Django that is edge case (for me, at least), the incentive for me to spend my spare time hunting down the underlying problem is quite low. So - if you want to help, jump right in. Pick a problem and triage it. Make sure the ticket has all the characteristics above, and mail django-developers indicating that you have triaged a ticket, and recommend a course of action (with reasoning). At first, this may require you to be persistent - if you find that your pet ticket isn't gettng attention, occasional polite requests for eyeballs may be necessary. Once that problem has been resolved and committed, pick another problem. As you earn a reputation for good triage work, your 'triage complete' messages will work their way closer to the top of my (and other committer) to-do lists, and you should find that less pestering is required to get the attention of a committer. So - there's 175 bugs with patches, and the only way to kill them is one at at time. Have at it :-) Yours, Russ Magee %-) [1] Note that 'non-trivial' doesn't just mean 'only affects 1-2 lines of code' - it also includes the fact that the lines that are being modified don't have a significant follow-on effect on the overall design of Django. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
