Ah! <span></span>Thanks for posting this, I knew Joel had something like this but I couldn't find it anymore.<br><br>On Tuesday, 14 May 2013, Gonzalo Odiard wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I agree with the need of cleanup the bug database. I have proposed that several times,<div>and closed many bugs. One of the best arguments I read about this topic,</div><div>is the "bug bankrupcy" description:</div>
<div><br></div><div>"<strong style="line-height:20px;font-size:medium;background-color:rgb(245,244,223);font-family:Georgia,serif">The bug database</strong><span style="line-height:20px;font-size:medium;background-color:rgb(245,244,223);font-family:Georgia,serif"> 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?</span>" [1]</div>
<div><br></div><div>I have prepared two reports to try to understand better our actual situation:</div><div><br></div><div>Bugs by components [2]</div><div>This report show activities are usually in a good shape (that was not always true)</div>
<div>Of course, sugar* + journal are much more complex. </div><div>If we do some triage, should be good concentrate on these components</div><div><br></div><div>Bugs by sugar version [3]</div><div>
Nobody is working in fix bugs of sugar older than 0.98.</div><div>We should check if the older bugs are still present or close them.</div><div><br></div><div>Gonzalo </div><div><br></div><div>
<br></div><div>[1] <a href="http://www.joelonsoftware.com/items/2012/07/09.html" target="_blank">http://www.joelonsoftware.com/items/2012/07/09.html</a> </div><div>[2] <a href="http://bugs.sugarlabs.org/report/14" target="_blank">http://bugs.sugarlabs.org/report/14</a></div>
<div>[3] <a href="http://bugs.sugarlabs.org/report/13" target="_blank">http://bugs.sugarlabs.org/report/13</a></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 14, 2013 at 11:21 AM, Walter Bender <span dir="ltr"><<a href="javascript:_e({}, 'cvml', 'walter.bender@gmail.com');" target="_blank">walter.bender@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Tue, May 14, 2013 at 9:23 AM, Daniel Narvaez <span dir="ltr"><<a href="javascript:_e({}, 'cvml', 'dwnarvaez@gmail.com');" target="_blank">dwnarvaez@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tuesday, 14 May 2013, Walter Bender wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>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</div>
</div></div></div></blockquote><div><br></div><div>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.<span></span> </div>
</blockquote><div><br></div></div></div><div>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.<br>
<br></div><div>-walter<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><font color="#888888">
<br><span><font color="#888888"><br>-- <br>Daniel Narvaez<br><br>
</font></span></font></span></blockquote></div><div><br><br clear="all"><br>-- <br>Walter Bender<br>Sugar Labs<br><a href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a><br>
</div></div></div>
<br>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="javascript:_e({}, 'cvml', 'Sugar-devel@lists.sugarlabs.org');" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br></blockquote></div><br></div>
</blockquote><br><br>-- <br>Daniel Narvaez<br><br>