L10n:QA

We'd like to get a rough idea on how the particular locales can do QA, which resources they have, how fast, how many eyeballs, etc. Please just add a === ab-CD == beneath, and explain how long it takes you to do which kind of QA on which platforms. We'd like to know which platforms are tested within the l10n team, and which are covered by community QA as well.

de

We are using the locale-inspector tool and compare-locales.pl scripts.

Thunderbird QA: Is done by mail owner using latest branch builds (or rc candidates) for daily usage (win32; POP, IMAP, RSS, Newsgroups) and running these smoke tests for win32 (Win XP Pro) and linux (OpenSUSE 10.0). OS X QA is done by Martin Creutziger and a second team member. Furthermore all Thunderbird Mail DE team members (9+) are testing branch builds and we have feedback in german forums and in BugZilla de-AT component. The smoke tests (win32 and linux) could normally be done in less than 24 hours.

Firefox QA:

es-AR

QA made by five members of the l10n team. Some community feedback is received, but there's no community group testing. Testing is done as soon as needed. Less comprehensive testing is made when changes are made to the CVS. We do thorought testing on Windows Platforms (9x and XP), some of us use nightlies in daily work to test them in the wild. We do limited testing on Linux Platforms, as we don't have enough linux boxes in the team. We don't test Mac builds, as we don't have access to any Mac. Community QA is almost entirely done on Windows.

ga-IE

2 Mailing Lists:
- 1 private used mostly by translators.
- 1 public for mostly users (http://gaeilge.mozdev.org/list.html)
For Beta and Full releases, we have at least 2 testers on each of the major platforms (Linux, Mac, Windows). Tested is heavy and comprehensive, mainly comprised of users using it as their default browser/mail and trying as much functionality as possible.

nb-NO

Forum for public discussions, and internal mailing lists. Rough estimate 20-30 visitors in forum each day. No fixed way of doing QA -- module owner is fully responsible for integrity of check-ins. Core team does testing on Windows and Linux; 2 random external users do mac release testing. Some feedback has been received on nightlies; we have gotten around 5-10 feedbacks on translation last month, which we interpret to that there is a error-reporting base of some size. Owner makes most of the testing in front of releases, primarily on Windows, which averages around 30 minutes of "use".