RetroSearch Browse

Sat Feb 23 00:03:34 CET 2008 · https://mail.python.org/pipermail/python-dev/2008-February/077122.html

"Martin v. Löwis" writes:

 > That's why the entire field is called "Resolution". "duplicate",
 > "invalid", "out of date", "wont fix" and "works for me" are also
 > firm decisions.
 > 
 > ("later", "postponed", and "remind" might not be firm decisions -
 > they were just inherited from SF).

These latter three are not resolutions, and IMO should be removed.
Items with those "resolutions" should be considered still active (or
perhaps "pending" auto-closure).

Specifically, the "name" field of the corresponding items in the
relevant class should be edited so that in legacy issues containing
them they are displayed as "- not yet resolved -" or "- no selection -".
(I'm not sure it's wise, or even possible, for multiple items to have
identical names, though.  If not, they can be uniquified in some way.)

Then these items should be retired so that they won't appear at all in
menus.

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

Showing content from https://mail.python.org/pipermail/python-dev/2008-February/077122.html below:

[Python-Dev] Small RFEs and the Bug Tracker