Weekly report

[Tony Mansson]

Hello,

Please take a few minutes and fill in your reports.

Note that the team status is distributed widely and is of great interest
for many stakeholders. The team status is what I extract from your reports,
and the more I have to work with, the better it can get. So please don't be
too terse, use a couple of more words than the absolute minimum for a full
English sentence:)

This is also a good opportunity to check your bugs and blueprints. Make
sure they are up-to-date and reflect reality. If nothing has happened to
the work item, maybe there is a story behind this that can be told as a
comment?

For the bug reports, If you have managed to resolve a bug and can put it in
state "Fix Committed" Please make sure the following data is included:

- Reference to an official build that has been verified to not have the bug
- An explanation of how this verification took place.

Personally I also appreciate when someone explains how the root cause was
found. Such knowledge sharing can help other team members, and it can
reassure sceptics that the applied logic is sound.

Example:
Bug title: Feature X does not work on board Y.
Final comment: Feature X works on build Z for board Y, verified by
demonstrating that App Q now can play a .xyz file. The reason was an
overflow in the 16-bit beancounter, and the bug was found
by examining logcat output when decoding .xyz files with increasing sample
rates. A collection of good test files is found at: http://url.com.

BR,
Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linaro.org/pipermail/linaro-android/attachments/20120221/4523a646/attachment.html>