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: Is done by browser owner using latest branch builds (or rc candidates) for daily usage and running appropiate parts of these smoke tests for win32 (Win XP Pro) and linux (Ubuntu 5.10). OS X QA is done by Martin Creutziger. Furthermore our large userbase is testing branch builds on a daily basis 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.

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.

hu

Hungarian l10n team consist of one active member (project owner). A few other people helped him with the translation, but not actively participated in the QA process in the past few weeks. The locale-inspector tool and compare-locales.pl scripts are used. Some feedback (useful comments) have been received from the users' community.

Firefox QA: Full L10N QA including accesskey checks and check for truncations was performed by a community member on Linux, Mac and Win. The project owner and a few other people he knows use Firefox 1.5 nightlies, betas and/or RCs on a daily basis as their primary browser.

Thunderbird QA: Thunderbird QA was done by the project owner. RC1 was tested on Windows platform (have been used as the primary mail application for a while). Linux and Mac have not been tested.

ko

The Korean community has own forum and volunteers(10~20) to help QA. And there re two l10n committers and two tree committers. Maybe 20 people can help QA for korean version. About 5 people have macintosh and 3 people have linux system. Also Channy, a module owner of ko locale have all system of window, mac and linux.

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".

pl

Firefox: compare-locales is used to keep locales in sync with en-US. QA done by browser owner (Marek Stepien) using latest Linux branch builds (including rc2-candidates) for daily usage, and running smoketests a few times a month; Occasionally browser owner also tests Windows and Mac builds. Other AviaryPL team members use nightly builds on Windows and Linux for daily usage.

The smoke tests (Linux and win32) can normally be done in less than 24 hours.

Some community members are also using nightlies and reporting problems in our forums, our bugzilla or the alt.pl.mozilla Usenet newsgroup. This includes translation feedback.

Thunderbird: Bonsai is used to track changes in en-US and pl, tinderbox is used to make sure everything is OK. Mail owner (Piotr Komoda) is doing global in-use application and translation testing one or two times per month using newest Windows nightly build. Occasionally mail owner also tests Linux builds. Mac builds testing is done by our MacOS specialist (Piotr Chylinski, Camino l10n owner). Before each release translation is massively tested in three ways:
1) Couple of our in and outside team QA testers are checking language files
2) Our head QA (Wojciech Kapusta) is testing translation by checking (literally) every part of UI looking for grammatical, stylistic and comprehensibility issues.
3) Information is posted in our forums calling for community testing.