[Dev] On bug resolutions
heikki at osafoundation.org
Fri Sep 10 09:40:18 PDT 2004
I've seen some confusion over bug resolutions, so I thought I'd write
how I interpret them:
FIXED - The bug was fixed and you can actually point to the checkin or
other action that fixed it.
WORKSFORME - A miracle happened. It started working, but you can't
figure out for sure what fixed it.
LATER - Should not be used. Set target milestone "Future" instead. The
reason is that a bug that is marked LATER is basically never seen again
and gets lost (the default query values never show it and people never
remember to query for it).
WONTFIX - There is a reason why this bug is not going to be fixed, and
why it should never actually be fixed even if somebody else thought it
might be a good idea. The wontfix reason should clearly state why it
should never be done. If it is something we won't be doing now, but
maybe in a year or two, set target milestone "Future".
INVALID - The bug does not make sense, or there was some
misunderstanding. Either it was invalid already when it was failed, or
things changed so that it became invalid. An example of the latter
happening is for example a bug in some 3rd party library which becomes
invalid if we remove the 3rd party library from the build.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 249 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20040910/6f479787/signature.pgp
More information about the Dev