perfsonar development work

["Michael Bischoff" <>]

> 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 agree with jochen, closed means it's verified by a 2th party. On top of 
that one might
wants to research if there is the possibility to write a test case to check 
for regression. I
do not know how gn3 is compartmentalised, perhaps there is a group envisioned 
for doing that
stuff, I can only hope.

But speaking about clean up - there are other parts that could use some love 
too. I'll skip
the lobbing for more build infrastructure and skip to the more important 
parts: wiki websites
several q&a and knowlages bases, their lack of target(developer, system 
admin, end user)
crowd and navigability/discovery. etc Am I alone with this sentiment?

Kind regards,

Michael