RetroSearch Browse

Fri Sep 24 16:31:00 CEST 2010 · https://mail.python.org/pipermail/python-dev/2010-September/104040.html

> > But we also have "performance", "crash", "resource usage"... Are we
> > suggesting we devise a separate list box for each of these issue types?
> 
> I must admit, I've never actually found much use for those additional
> options. If I'm flagging a bug I'll nearly always mark it "behaviour",
> otherwise I'll mark the issue "feature request". The characterisation
> of "what *kind* of bug is it?" is something that can usually be left
> until later in the process.

I have often used searches on "performance" or "resource usage" to find
what was needing a review or a patch. I think it would be a mistake to
remove those two categories.

Regards

Antoine.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-September/104040.html below:

[Python-Dev] Goodbye