QA meeting
Line 12: | Line 12: | ||
* QA is good. | * QA is good. | ||
- | * The criteria are a good start, but need tweaks | + | * The criteria are a good start, but need tweaks |
* The packages UI needs some streamlining for testers. | * The packages UI needs some streamlining for testers. | ||
* As a tester, a better reminder of the checklist when checking | * As a tester, a better reminder of the checklist when checking | ||
Line 19: | Line 19: | ||
"release early, release often" when fixing bugs or introducing new | "release early, release often" when fixing bugs or introducing new | ||
small features (i.e. karma resets to zero). | small features (i.e. karma resets to zero). | ||
+ | * We need a mechanism to preserve karma or reset it to zero. |
Revision as of 18:55, 4 November 2009
QA Meeting Agenda
Please place the things you wish to discuss at the QA meeting on IRC below.
Meeting details
- IRC: irc.freenode.org
- Channel: #maemo-meeting
- Time: Tuesday, November 10th, 14:30 UTC
Agenda
* QA is good. * The criteria are a good start, but need tweaks * The packages UI needs some streamlining for testers. * As a tester, a better reminder of the checklist when checking would be good. I also like the ease with which I can give feedback. * As a developer, I don't *think* I want to be constrained with "release early, release often" when fixing bugs or introducing new small features (i.e. karma resets to zero). * We need a mechanism to preserve karma or reset it to zero.