I spent some time looking through RESOLVED > INVALID bugs to see how they are being used. The vast majority are for closing bug reports that were upstream/downstream, no response from reporter, or not a bug to begin with. It appears renaming INVALID to NOTABUG would be a good change, as some of the other bugs that have been closed as RESOLVED > INVALID would be better served under RESOLVED > WORKSFORME (bug report with no response from reporter) or RESOLVED > UPSTREAM (bug report with problematic Nvidia drivers) or RESOLVED > DOWNSTREAM (bug report with distro problems).
Regarding closing wishlist items with, I believe RESOLVED > LATER is a good choice, it appears others are already doing that. Here is my follow-up change recommendation based on feedback and research: UNCONFIRMED -> REPORTED WONTFIX -> INTENTIONAL INVALID -> NOTABUG Andrew Crouthamel ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On 6 September 2018 1:57 PM, Karl Ove Hufthammer <k...@huftis.org> wrote: > Andrew Crouthamel skreiv 05. sep. 2018 23:49: > > > Does anyone else have comments on status names? The name itself or yay/nay > > on renames? > > Here are some updated proposed names based on feedback and thesaurus > > searching: > > UNCONFIRMED -> REPORTED or OPEN > > WONTFIX -> ASDESIGNED or INTENTIONAL > > INVALID -> NOTABUG or ERRONEOUS > > I like REPORTED and INTENTIONAL. And if underscores are allowed, I would > prefer them, e.g. NOT_A_BUG. > > -------------------------------------------------------------------------------------------------------- > > Karl Ove Hufthammer
