L10n:Thunderbird 1.5 Release Status

Quick Notes

mscott -> I filled in COMMUNITY field for the intended testing level for a bunch of locales which will be relying on the community to help test. That was just my initial best guess. Will probably add more to the list. MoCo QA, feel free to adjust.
mscott -> I just conducted an initial trademark review via lxr to get a feel for how many locales had work to do (12/08)
Should we add a color to a locale row after it has owner sign off, trademark review and has been moved to the candidates directory so QA knows it is ready for the next step? Or do we need a new column that implies the build is now in the candidates directory ready for testing?

Now on to the details...

First, localization teams (owners and QA volunteers) grab the current nightly build.
The L10n owner signs off on a locale and includes information about what was tested on L10n:Thunderbird_1.5_Sign_Offs.
Axel and mscott perform a Trademark Review for the locale, detailed results are on L10n:TB_1.5_Trademark_Review.
If the build passes trademark review, mscott or Paul will copy the locale into the 1.5rc2 candidates directory and will add it to this table.
Moz QA will determine the level of additional testing for each locale. Community only testing is a valid answer for many of the locales. For some subset of locales (3-5), Moz QA may run the l10n tests. QA will mark the build as PASS when this is done.
Axel/mscott will mark the build as being ready for release after QA has passed it.
At the time of the release, the release team can look at the release status column to know when locales are ready for release.

Owner Signoff --> PASS for locales which the localization owner has signed off on. No value for locales still waiting for owner signoff. (axel/mscott will change this column)
TM Review Status --> PASS for locales which have passed trademark review. FAIL for locales which had problems (problem details are likely on L10n:TB_1.5_Trademark_Review). No value for locales which have not been reviewed. (axel/mscott will change this column)
Testing Level --> COMMUNITY for locales which we are relying on the localization owner. IIT (install & ID test). L10N_CHECKLIST for the few locales we intend to run the full l10n checklist steps on ourselves. (values to be determined by QA, Axel and mscott)
MoCo QA Status --> PASS / FAIL (with reasons) / no value for locales which have not been looked at. (QA will change this column)
Release Status --> READY for locales ready to be released. READY (sim). RELEASED for locales which have been made live for the 1.5 release. (Axel/mscott and the release team will change this column).

See color codes at the bottom

Locale	Owner Sign-off	TM Review Status	Testing Level	MoCo QA Status	Release Status
bg Bulgarian		PASS post-RC2	COMMUNITY		no build date
ca Catalan	PASS	PASS	COMMUNITY
cs Czech		PASS	COMMUNITY
da Danish		PASS	COMMUNITY
de German		PASS
el Greek	YES, needs verification	PASS maybe-post-RC2	COMMUNITY
en-GB UK	YES	PASS	COMMUNITY
es-AR Argentina		PASS	COMMUNITY
es-ES Spain		PASS
eu Basque	YES	PASS	COMMUNITY
fi Finnish	YES	PASS	COMMUNITY
fr French	YES	PASS
ga-IE Irish		PASS	COMMUNITY
gu-IN Gujarti		PASS	COMMUNITY
he Hebrew		PASS	COMMUNITY
hu Hungarian	YES	PASS post-RC2	COMMUNITY
it Italian	YES, need verification	PASS
ja-JP-mac Japanese		PASS
ja Japanese		PASS
ko Korean		PASS post-RC2			2005-12-21 13:52
mk Macedonian		PASS	COMMUNITY
mn Mongolian		PASS	COMMUNITY	FAILED, build orange
nb-NO Norwegian	YES	PASS	COMMUNITY
nl Dutch	YES	PASS
nn-NO Norwegian		PASS	COMMUNITY	FAIL, no builds
pa-IN Panjabi		FAIL mailnews.hints_and_tips.url points to http://texturizer.net/thunderbird	COMMUNITY
pl Polish		PASS	COMMUNITY
pt-BR Portugese Brazil		PASS
ro Romanian		FAIL, bad start_page.url	COMMUNITY
ru Russian		PASS	COMMUNITY
sk Slovak		PASS, maybe-post-RC2	COMMUNITY
sl Slovenian	YES	PASS	COMMUNITY
sv-SE Swedish		PASS	COMMUNITY
tr Turkish	YES	PASS	COMMUNITY
zh-CN Chinese simplified	YES	PASS	COMMUNITY
zh-TW Chinese Traditional		PASS	COMMUNITY