I'm still in favor of adding the "needsinfo" resolution and would love to
see that happen... I guess technically I could even do that one myself via
Trac's web admin if we're all agreed on it.
I'm ambivalent about adding the "ticket type" field back in, though. It can
be useful, but it *is* an extra item to keep managed and argue about... My
bigger concern, though, is the 1700+ existing tickets which will be
uncategorized. It would end up meaning that using that flag for queries in
Trac wouldn't give you a complete picture (at least not for a very long time
while things catch up).
All the best,
- Gabriel
--
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
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
