I guess I'll jump in and start triaging. What about a ticket like this: http://code.djangoproject.com/ticket/2284
Super-ambiguous. There are dozens of tickets like this that are frozen in time with no way for anybody to know what's going on. Maybe there just needs to be a better way to handle this type of ticket? Regards, Adam On Apr 22, 4:33 pm, Jeremy Dunck <jdu...@gmail.com> wrote: > On Thu, Apr 22, 2010 at 3:26 PM, Gabriel Hurley <gab...@gmail.com> wrote: > > On Apr 22, 1:21 pm, Adam Nelson <a...@varud.com> wrote: > > >> 2. Assign all of these tickets to 1.3 and nothing else: > > >>http://code.djangoproject.com/query?status=new&status=assigned&status... > > > Awwww, only 900 tickets to work through for 1.3? Don't go too easy on > > the core team! ;-) > > To be clear, this is why the triage process exists. We need more > people to look at tickets, review them for the standards that Django > has set (good code, test coverage, documentation for any new features) > and mark them "ready for checkin". > > The subset of tickets that achieve "ready for checkin" then take a > commiter's time for final review and merge. > > -- > 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 > athttp://groups.google.com/group/django-developers?hl=en. -- 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.
