Peter Memishian wrote:
> > > (Now if only I could go back and edit my comment to use that ;)
> >
> > i know you're smiling, but, for the record, this isn't bugster,
> > you can't :).
>
> In general, people should be tolerant of errors and only correct
> comments if it's really necessary.
In my experience (as a submitter/RE for roughly two thousand Solaris bugs)
I *often* need to go back and revise previous entries in order to keep the
problem and solutions statements clear and correct as new information
comes to light. This is especially important for other organizations such
as support and sustaining that use the bug reports to identify and address
issues that exist in older releases. Unclear or incorrect statements in
bug reports cost Sun money and cost customers time.
If this is not supported with Bugzilla, I'd put it on my "must have" list.
+1
It's not that unusual to have information in the initial description of
a bug that turns out to be wrong and extremely misleading. For simple
factual errors [1], I'd much rather have accurate information in the
initial report rather than read a correction 10 comments later.
And, of course, we have to have a way to remove confidential information
that accidentally gets posted in a public place.
Scott
[1] To be clear, I'm talking about correcting misstatements to avoid
wasting everyone's time, not removing debugging hypotheses that didn't
pan out or anything like that.
--
Scott Rotondo
Principal Engineer, Solaris Security Technologies
President, Trusted Computing Group
Phone/FAX: +1 408 850 3655 (Internal x68278)
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
