To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108150


User azadian changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|CLOSED                    |UNCONFIRMED
--------------------------------------------------------------------------------
              Resolution|INVALID                   |
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Tue Jan 12 12:58:29 
+0000 2010 -------
This is what we call "proof by erasure."  The fact that I can't reproduce this
bug at will does not mean that it does not exist.

By setting the resolution to INVALID you are either denying the veracity of my
report, or saying that it is not a problem.  I hope you don't mean either of
those, which means that the resolution is wrong.

WORKSFORME would be a valid status, CLOSED is not.  Of course this would imply
that somebody actually looked at the code with this report in mind.

As a programmer I am fully aware that this kind of bug report is difficult to
deal with.  OTOH, these kinds of reports can be invaluable when tracking down
those really nasty bugs.

I suggest that this kind of cavalier handling of bug reports does not encourage
people to take the time to submit them.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to