Bug#344831: DevRef: Please document best practice for submitters testing bugs
Hi,
On Mon, Dec 26, 2005 at 02:01:18PM -0500, Justin Pryzby wrote:
> Package: developers-reference
> Severity: wishlist
>
> Do you think it would be worthwhile to include some documentation to
> the following effect, perhaps added to either 5.8.2 or 5.8.3?
>
> It is best to close bugs only when the submitter agrees that it
> should be closed.
I do not think this is the standard practice. Closing bug properly with
####-done@b.d.o will send notification to submitter anyway. IF
submitter disagrees, bugs can be always reopened.
I do not mind stating something alon:
The developer should ensure bugs are fixed when closing bug reports.
The developer should refrain from closing bug reports when submitter
disagrees with reason and should leave them on BTS with the "wontfix"
tag.
> Oftentimes during bug triage, stale bugs are
> discovered which may have been fixed many releases ago, but which
> remain opened.
Yes, that is why we ask submitter to test it. In case of no reply, I
think it is discression of DD to keep or close depending on each
situation.
> Sometimes, the report is short and simple, and it is
> easy to check whether the bug still applies. Other times, the
> discussion in the bug log is long and documents requests by various
> people.
Setting generic rule is difficult, I think....
> In any case, it is good to have the submitters approval
> that the reported problem has been solved.
It will only clutter BTS and overload DD's work with non-significant
benefit if we enforce such an best practice. If DD is convinced with
reason, he should be allowed to close it without submitter's approal.
As I said, sbmitter can reply to reopen bug.
Osamu
Reply to: