On Sun, 2006-02-26 at 20:21 -0800, Jacob Kaplan-Moss wrote: > Howdy folks -- > > Four days of PyCon sprints start tomorrow! A bunch of us here at PyCon > met this afternoon to plan out what we'll be working on over these next > four days. You can find those topics and notes from our meeting today > at http://code.djangoproject.com/wiki/PyConSprint06.
Cool! Nice list. :-) I noticed one item is "Review and apply outstanding patches" (which I'm happy about) and it reminded me of something I've been meaning to ask. On other Open Source projects I've worked on, there has been a way to indicate in the bug tracking system that a patch was attached to a report. Either by adding [patch] to the title or setting a "patch" keyword or something similar. How manageable is the current number of the Django bug reports? Would it make it easier for people like Adrian who have to do the ultimate review if we add something like this, or is the volume low enough that you can stay on top of it manually? As I write this, there are 338 open tickets, some of which have patches, some don't. That's a lot of reading to find the ones with patches, so is there some way we -- the bug reporters and sometime patch producers -- can help out here? Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
