perfsonar development work

[Jochen Reinwand <>]

Hi,

On Tuesday 10 March 2009, Szymon Trocha wrote:
> Antoine Delvaux pisze:
> > Being in the process of setting up the psUI v0.15 testing plan, I had a
> > look at the bug listing in https://bugzilla.perfsonar.net/  The list of
> > 'resolved/verified but not closed' bugs is quite long: 384, for only 155
> > closed bugs.
> >
> > Is there any specific reasons for not closing those bugs?  This long list
> > reduces bugzilla usability forcing us to use very specific queries before
> > finding relevant bug listing.
>
> Fully agree. I also urge all developers to put more attention to track
> their bugs (assign status, comment, fix, close). This is one of the
> developers' duty.

I do not fully agree here! Closing a bug is not (necessarily) the duty of a 
developer! A developer is setting it to resolved. If he/she is also 
responsible for closing it, it would be useful to just set closing instead of 
resolved. There is a good reason why there are two states, solved *and* 
closed.

I see three possibilities for a bug to go from solved to closed:

1. The reporter of a bug sets it to closed, when he/she is satisfied with the 
fix.

2. There is a person responsible for keeping track of bugs and is also doing 
the communication work with the user that reported the bug (QoS contact?).

3. There is a time span after which a bug is more or less automatically 
closed 
if nobody complains, that the fix isn't working.

I think we should allow all three possibilities. But none of them is really 
developer driven. Except for the last one. This can, of course, also be done 
by the developers.

Just my 0.02 EUR

cheers,
Jochen

-- 
Jochen Reinwand, DFN-Labor
Friedrich-Alexander-Universität Erlangen-Nürnberg
Regionales RechenZentrum Erlangen (RRZE)
Martensstraße 1, 91058 Erlangen, Germany
Tel. +49 9131 85-28689, -28800, Fax +49 9131 302941

www.win-labor.dfn.de