On Mon, Mar 28, 2011 at 8:04 PM, Julien Phalip <jpha...@gmail.com> wrote: > On Mar 28, 10:49 pm, Karen Tracey <kmtra...@gmail.com> wrote: >> +1 on having a distinction between bug, feature, and optimization. >> >> I don't think both "Uncategorized" and "Other" are necessary. > > My reasoning for "Other" was that there might be things that are > neither a bug, a feature or an optimisation. I admit that I can't > think of any specific example for it right now, but I thought there > might sometimes be general tasks that do not require a code change -- > but maybe that's never the case and therefore not necessary? > > And the default "Uncategorized" was for when the reporter could not > decide or simply didn't bother (which is still better than picking a > wrong option).
I agree with Karen on "other" -- Bug/Feature/Optimization is a pretty comprehensive list, so "other" is a bit YAGNI. However, I agree that "uncategorized" is needed as a default state. Ok - so at this point, the option list is looking like: * Uncategorized * Bug * Release blocking Bug * New Feature * Optimization 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-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.
