On Mon, Mar 28, 2011 at 2:12 PM, Julien Phalip <jpha...@gmail.com> wrote: > Hello, > > I'm not sure if the consensus so far is either "Meh" or "Let's give it > a try", or if there's even a consensus. I'm still keen on the idea but > I don't want to insist too much if it doesn't gather enough support, > so I'll re-submit it here one last time. The latest proposal is to > introduce a new "Type" (or "Nature" or "Kind"...) field in Trac with > the following options:
FWIW, I agree it's worth doing. However, * I'd like to see some feedback from other core team members, and * I can't make these changes myself -- they require someone with access to the Trac install, and that isn't me. > * Uncategorized (default) > * Feature request: for adding something new. > * Bug report: for when an existing thing is broken or not behaving as > expected. > * Optimisation: for when an existing thing is not broken but could be > made better, faster, stronger. > * Other: none of the above. I would suggest two modifications to this: First, I would call "Feature Request" -> "New Feature" to remove any suggestion that just by opening a ticket, it will magically be implemented by the feature ponies. Second, this ontology doesn't do the one type of filtering that we need for release management -- identifying bugs that are release blocking. This means that either the 'bug report' category needs to be expanded into: * Bug * Bug causing data loss * Regression * Bug with new feature Or we need to add a separate boolean flag for "release blocker". We used keywords for the 1.3 release, and I think that proved a helpful resource; I think it's worth promoting these to full UI elements. 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.
