On Mon, Mar 28, 2011 at 10:32 PM, Luke Plant <l.plant...@cantab.net> wrote: > On 28/03/11 13:21, Russell Keith-Magee wrote: > >> Ok - so at this point, the option list is looking like: >> >> * Uncategorized >> * Bug >> * Release blocking Bug >> * New Feature >> * Optimization >> >> Yours, >> Russ Magee %-) >> > > I'm definitely +1 on this new field, and just sat down in order to push > it forward, if Julien hadn't beaten me to it :-) > > Regarding splitting up bug/release blocking bug, I don't think it's a > great idea because it makes it harder to search for simply 'bugs', and > it means we are mixing up release process concerns with an entirely > orthogonal question i.e. the nature of the bug. > > We can cover the nature of the bug more flexibly by using keywords, like > we already do with 'regression' and 'blocker', and we can search on > these easily, as I've done at bottom of the new reports page: > <http://code.djangoproject.com/wiki/Reports>
My problem with marking regression and blocker as a keywod is that you're a 1 character typo away from a ticket never showing up in a relevant query. Regressions/blockers are a core part of our process; IMHO that means they should have first class representation in Trac that can't be mistyped or misinterpreted. I'm not convinced we need to differentiate blocker from regression. I know we started doing this as part of the 1.3 process, but with the benefit of experience -- all regressions are blockers, and the ticket description or discussion will usually provide any extra context that is required. I'm not sure the distinction gains us anything. However, I accept your point about splitting bug into two categories. Making it two different flags was a suggestion for expediency of implementation, but I can see how it will complicate your life with reports. So I suppose we'll just have to hunt down someone with access to the server to add the 'blocker' flag, and as an interim, continue to use keywords. 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.
