Michael Blake added a comment - 23/Oct/06 01:14 PM

Michael Blake added a comment - 23/Oct/06 01:14 PM Generally speaking, a bug with a resolution code of 'deferred' should not be closed. Bugs 'closed' with a resolution code of 'deferred' are carry overs from the old bug tracker. If you see something you think should be open, but all means reopen it. Ideally, we'd review all unresolved bugs while preparing for an upcoming release. Those to be included would be be opened (start progress) and given a target fix version, those that will never be fixed would be resolved with an appropriate resolution code (won't fix, duplicate, etc) then closed. Those deemed to be fixed at a later date (a later release) would get a resolution code of deferred (but not closed). The problem we face at this time is thousands of unresolved bugs and not enough people to review and make informed calls on how to handle them.

Michael Blake added a comment - 06/Oct/08 03:13 PM

Michael Blake added a comment - 06/Oct/08 03:13 PM Closing as this is no longer relevant. I wouldn't close a bug with a resolution code of "deferred" if I wanted the issue to be resolved in a later release.