Bug#344831: DevRef: Please document best practice for submitters testing bugs

[Justin Pryzby <justinpryzby@users.sourceforge.net>]

On Sat, Dec 31, 2005 at 11:46:44AM +0900, Osamu Aoki wrote:
> 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.  
Part of my motivation is from the result of reading apt-listchanges
output and finding bugs closed which shouldn't have been closed.

Either wrong bugs closed (wrong package even!), bugs not close, bugs
closed by not related to upload, etc.  Not to mention submitters who
are at a new or temporarily-down email address.

I'm not sure that the devref edit will help at all, or that it is the
right way to go about it.

> 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.
This doesn't accomplish much of what I want.

> In case of no reply, I think it is discression of DD to keep or
> close depending on each situation.
Agree.

-- 
Clear skies,
Justin