[maemo-developers] maemo Bug Jar #4

[From: quim.gil at nokia.com]

Thanks! Very useful already and hopefully it will be even better as we
do more Jar iterations.

Suggestions for improvement:

- Separate bugs and enhancement requests properly, since they have
different degrees of urgency, the level of responsibility on them is
different and in fact they follow different processes internally. It is
not always easy to differentiate a bug from a feature request and many
enhancement requests are minor and totally based on small fixes a
developer alone can do, but this is the work of the persons dealing with
the bug report, not a problem in this report.

This is most visible in the "Ten biggest open bugs by number of votes"
and "Ten biggest open bugs by importance", where each enhancement
request there is actually taking the place of a bug that would deserve
more visibility. otoh it is easy to generate top 10 feature requests
tables.

- Highlight what is new and major-critical-blocker. Sometimes it helps
addressing issues sooner and better, sometimes it helps assigning the
right severity.

- Of course graphs showing the basic history are always useful. For
instance, having trends, seeing if things go better or worse, see the
impact of i.e. the Diablo release in the numbers... All this would help
us pointing out to people inside Nokia what is going on in the wide
picture.
 
>This summary is also available on Internet Tablet Talk:
>http://www.internettablettalk.com/forums/showthread.php?p=18182
>1#post181821

What about keeping the history in the new maemo.org MediaWiki.

Thanks again for your time and help.

--
Quim Gil
marketing manager, open source
maemo software @ Nokia