[Sugar-devel] Github issue tracking

[Gonzalo Odiard]

I agree with the need of cleanup the bug database. I have proposed that
several times,
and closed many bugs. One of the best arguments I read about this topic,
is the "bug bankrupcy" description:

"*The bug database* is obviously a great thing to have. Bug reports should
be complete, accurate, and actionable. But I have noticed that in many
real-world companies, the desire never to miss any bug report leads to bug
bankrupcy, where you wake up one day and discover that there are 3000 open
bugs in the database, some of which are so old they may not apply any more,
some of which can never be reproduced, and most of which are not even worth
fixing because they’re so tiny. When you look closely you realize that
months or years of work has gone into preparing those bug reports, and you
ask yourself, how could we have 3000 bugs in the database while our product
is delightful and customers love it and use it every day?" [1]

I have prepared two reports to try to understand better our actual
situation:

Bugs by components [2]
This report show activities are usually in a good shape (that was not
always true)
Of course, sugar* + journal are much more complex.
If we do some triage, should be good concentrate on these components

Bugs by sugar version [3]
Nobody is working in fix bugs of sugar older than 0.98.
We should check if the older bugs are still present or close them.

Gonzalo


[1] http://www.joelonsoftware.com/items/2012/07/09.html
[2] http://bugs.sugarlabs.org/report/14
[3] http://bugs.sugarlabs.org/report/13




On Tue, May 14, 2013 at 11:21 AM, Walter Bender <walter.bender at gmail.com>wrote:

>
>
>
> On Tue, May 14, 2013 at 9:23 AM, Daniel Narvaez <dwnarvaez at gmail.com>wrote:
>
>> On Tuesday, 14 May 2013, Walter Bender wrote:
>>>
>>> I think what would really help, independent of where/how we host things,
>>> is to instituteA more regular (and inclusive) triage meetings. I cannot
>>> think of the last time we had one that was announced on sugar-devel
>>>
>>
>> How did they go when they was organised? I think they would very helpful
>> if the community participates. If its just the same people which writes
>> code, then I think their time is better spent fixing bugs, reviewing and
>> writing automated tests.
>>
>
> We would have them in association with the release process. As I recall,
> we held them after feature freeze and again closer to the release date. It
> was in large part the coders, but not exclusively, and it gave others a
> chance to chime in regarding priorities. We'd generally meet for about 3
> hours on a weekend.
>
> -walter
>
>>
>>
>> --
>> Daniel Narvaez
>>
>>
>
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20130514/42f8d41f/attachment.html>