Summary: | Add a NEEDINFO resolution (to go with FIXED, WORKSFORME, etc.) | ||
---|---|---|---|
Product: | [Websites] bugs.kde.org | Reporter: | Matt Rogers <mattr> |
Component: | general | Assignee: | Matt Rogers <mattr> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | dmeltzer.devel, l.lunak, nicolasg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Matt Rogers
2004-09-17 06:47:10 UTC
Normally the state UNCONFIRMED is for "more info". Otherwise if a bug cannot be handled with the current information, in KDE it is typically changed to RESOLVED/INVALID. Have a nice day! yes, i'm aware of this. I've been a KDE developer for quite awhile now. However, why let these bugs sit as unconfirmed for months, and even years, when we can mark them RESOLVED/NEEDINFO and close them? They're not invalid bugs. If more info is provided, great! If not, then they're marked as resolved and people who look through bugzilla for something to work on have less to wade through. I don't think that INVALID is an appropriate status in those cases. Well, then you should perhaps report it to http://www.bugzilla.org/ so that it got added upstream. Have a nice day! why should i do this when we can easily customize our own bugzilla? RESOLVED REMIND works quite well for such cases :). Lubos, http://bugs.kde.org/bug_status.html says: REMIND: The problem described is a bug which will probably not be fixed in this version of the product, but might still be. So NEEDINFO is still necessary I think. Well Mr. Matt, you can maybe fix this yourself now :) yay for the new NEEDSINFO |