[maemo-community] Community Testing Squad (Sprint task:10.01-02)

From: Uwe Kaminski jukey at ju-key.de
Date: Tue Jan 26 10:13:06 EET 2010

I really do like this suggestions! One thing seems to be important for me:

Valerio Valerio schrieb:
 > * Testing Squad mailing list:
 >  - Public mailing list where are discussed any situation/issue/doubts
 > concerning the applications in the maemo.org <http://maemo.org>
 > repositories.
 >  - Receives a automatic notification for each packages that enters
 > testing, is demoted or is promoted.

if a package is promoted the should have to be a list of changes. Is 
there already a possibility in the publishing interface to put a change 
log or at least a link to the change log location inside of it?
It would really improve the efficiency of tests if the tester knows 
where are new features (I know that's not all... :)).

 > * Organized testing:
 >  - In each week one of the testing squad members is responsible for the
 > elaboration of a small list of apps that should be tested. We'll start
 > with a 5 a day (or 3 a day) approach in the beginning. Of course the
 > testers are free to test other apps or do all the testing in just one
 > day. The objective is have the apps tested by the end of the week.

3 or 5 a day sounds very much. Maybe we should classify the apps. A 
complex application should get 3 complex points a simple new desktop 
theme maybe only 1 complex point. Than it would be easy to say lets test 
apps with in sum 5 complex points. What do you think?

I'll put this comment also into t.m.o

Ciao Uwe
Uwe Kaminski
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3229 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.maemo.org/pipermail/maemo-community/attachments/20100126/f5f01ebc/attachment.bin>
More information about the maemo-community mailing list