Noted... sorry about the spam in that case :) D
On Aug 6, 10:52 am, Russell Keith-Magee <russ...@keith-magee.com> wrote: > On Fri, Aug 6, 2010 at 8:31 AM, David P. Novakovic > > <davidnovako...@gmail.com> wrote: > >http://code.djangoproject.com/ticket/13182 > > Let me know if there is anything else I can do on this ticket, it is fairly > > simple anyway. > > Hi David, > > Thanks for the patch submissions, but you don't need to send a message > to django-dev every time you upload a patch on a ticket. > > The django-updates mailing list gets notified every time a ticket in > Trac is updated, and most of the core team are subscribers to that > list. On top of that, Trac is ultimately a better source of data on > this, because it is much easier to search. > > There are two exceptions to this general rule: > > 1) You've fixed a bunch of tickets in a related area (e.g., 6 tickets > on bugs in select_related()). This makes a nice target for core > developer attention. It takes time to "spin up" on a given area of > code, especially in a complex area like the internals of the query > engine. If you can provide a bunch of tickets in the same area, it > means the 'cost' of spinning up can be spread over multiple tickets. > > 2) You've done some work on a particular ticket, but you haven't had > any response/review for a while. In this case, a gentle nudge/request > for review can help to grease the wheels. Again, if you have multiple > tickets, this makes the task more attractive. > > Please keep up the good work! > > 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.
