https://bugs.kde.org/show_bug.cgi?id=383753
--- Comment #6 from Christoph Feck <cf...@kde.org> --- > you fix bugs, not features. If a feature is added, the ticket is resolved as FIXED, so it is symmetrical to marking a denied feature with WONTFIX. You could demand a new resolution for features, such as IMPLEMENTED, ADDED, or whatever, but any missing feature is someone else's bug. > NOTABUG or CANTREPRODUCE > Yeah, but what resolution belongs to that? We also have WORKSFORME. Any type of closing a bug without a fix looks judgmental to the reporter, because he _has_ the issue, otherwise he would not have reported it. I keep most tickets open in the hope that with more eyes we find someone who understands the issue and can suggest a fix or a workaround, or can explain what the reporter did wrong. > Here's a bug that I close as invalid: > > https://bugs.kde.org/show_bug.cgi?id=384202 Looks okey. I also use NEEDSINFO+WAITINGFORINFO, if I am able to instruct the reporter what information developers could need to understand or further investigate the issue. If I do not get any reply after some 2+2 weeks, I give up and also set RESOLVED+INVALID, see e.g. bug 380361. I have been chasing bugzilla since nearly 9 years, and the only thing that I would change is merging "UNCONFIRMED" and "CONFIRMED" to a single state "OPEN". The distiction has cost us many man hours explaining that there is no difference to most developers. -- You are receiving this mail because: You are watching all bug changes.
