On 28/03/11 16:22, Luke Plant wrote: > On 28/03/11 15:50, Russell Keith-Magee wrote: > >> 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. > > An alternative would be to use the 'Severities' category, adding just > 'normal' (the default) and 'blocker'.
Having looked at it, that seems like a sensible way to go, so to keep this momentum, can I suggest the following. Enable the 'type' field: with: * Uncategorized (default) * Bug * New Feature * Optimization Enable the 'severities' field, with: * Normal (default) * Blocker As for the gardening, there are about 1700 open tickets that need the type setting. Those needing the severity field changing to 'Blocker' can be found more easily here: http://code.djangoproject.com/query?status=assigned&status=new&status=reopened&keywords=~regression&col=id&col=summary&col=keywords&col=status&col=owner&col=component&order=priority Can we get 20 volunteers to do this, and someone to volunteer to organise us all? I'm happy to spend time doing, say, 100 tickets. We could perhaps divide up by ticket number to avoid duplicating work, remembering that there are far more open tickets with higher numbers. Remember we can use the batch modify plugin to avoid sending 1000s of e-mails, but if you are not a Trac admin you'll need some permissions adding, probably temporarily, to use that feature. Regards, Luke -- If you can't answer a man's arguments, all is not lost; you can still call him vile names. (Elbert Hubbard) Luke Plant || http://lukeplant.me.uk/ -- 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.
