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>

Once this change lands, I'm been intending to split out most of the
existing reports on that page into bug/feature/optimisation, and that
would be made much less clean if we had both 'bug' and 'release blocking
bug'.

Luke

-- 
"If something is hard, it's not worth doing." (Homer Simpson)

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.

Reply via email to