Hi Sarah,
I was wondering the same thing myself. Following is the definition
of the "CLOSED" status field value [1]:
CLOSED - The bug is considered dead, the resolution is correct, and the
product the bug has been reported against is terminated or shipped. Any
zombie bugs who choose to walk the earth again must do so by becoming
REOPENED. This state is rarely ever used.
I would have thought that once a release is shipped that all bugs
contained in the release would move to the CLOSED state - but the last
sentence in the definition of the state seems to discourage its use. I
wonder whether VERIFIED is considered to be the most appropriate final
state.
Thanks,
Henry
[1] http://nagoya.apache.org/bugzilla/queryhelp.cgi#status
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
mailto:[EMAIL PROTECTED]
Sarah McNamara/Toronto/[EMAIL PROTECTED]
2003-11-25 06:01 PM
Please respond to xalan-dev
To: [EMAIL PROTECTED]
cc:
Subject: Xalan bugs in verified state. A general handling question.
I have a general question to the Xalan developers as to how we should be
handling the Xalan bugzilla reports that are marked as Verified. We
receive a report at xalan-dev (weekly I think) that informs us of the
reopened, new, verified and assigned bugs. I'm surprised that we have so
many bugs that are marked Verified. Should they not be moved to the
Closed state once they're verified? I don't mind doing the work to mark
them all, but I just wanted to check before hand to make sure that I don't
do something that I shouldn't do. I think it would make the reports more
useful as it would narrow down the report to the ones that do need to be
addressed.
Any comments?
The only downside to doing this cleanup is it will generate a whole bunch
of mail to the xalan-dev list which will be just fluff for most of our
readers.
Sarah McNamara
