On Tue, Mar 29, 2011 at 8:17 PM, Luke Plant <l.plant...@cantab.net> wrote: > On 28/03/11 13:04, Julien Phalip 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 > > I've thought of some things that might go in 'Other', or perhaps could > go in a category of their own: > > "Cleanup", which would include: > * removing unused code and imports > * removing support code for older Python versions. > * converting doctests to unittests > * some refactorings like removing duplication.
Personally, I could live with optimizations being included in this "Cleanup" group (or cleanups being included in "optimizations"... or a "cleanup and optimization" group... or a bikeshed). We're not looking to have a complex, fine grained ontology; we're just looking for a rough labels that lets us broadly categorize the stuff we have to do. Bug/Feature is the really important distinction. So, current proposal stands at 4 categories: * Uncategorized * Bug * New Feature * Cleanup/Optimization And 2 severities: * Normal * Release blocker Barring objection, I'll try to find some time this afternoon to introduce the new flags. (and, implicit in that -- I'm volunteering to spend some time processing backlog, too). 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.
