Closed Bug 300028 (fx105l10n) Opened 17 years ago Closed 16 years ago
ship Firefox 1
.0 .5/1 .0 .6 l10n builds
Collect and ship all ready l10n builds for Firefox 1.0.5. Use this bug as a tracking bug for pending localizations, as well. 1. Test builds found at http://mozilla.osuosl.org/pub/mozilla.org/firefox/nightly/latest-aviary1.0.1-l10n/ with the build date of July 7 or newer. For reference, MoFo QA is running this set of tests for the en-US builds http://testrunner.mozilla.org/test.cgi?run_id=1362 2. Build sign offs in this bug should be of the form: <locale> ready for staging Example: for cs-CZ: cs-CZ ready for staging If the locale isn't ready to ship, then note so by saying: <locale> not ready for staging 3. Each locale should have sign off on its builds only by their locale owner.
hu-HU ready for staging
sl-SI ready for staging
fi-FI ready for staging
tr-TR ready for staging
ro-RO ready for staging. Mac builds untested. Assuming they are OK, based on previous versions.
nb-NO ready for staging
it-IT ready for staging
cs-CZ win installer ready for staging
ru-RU ready for staging
el-GR ready for staging
You are testing 20050708 en-US builds. http://weblogs.mozillazine.org/qa/archives/2005/07/new_firefox_105.html Should we test with 20050708 l10n builds again? # aleady many locales says ready...
cs-CZ ready for staging
zh-CN Ready for staging. tested with 7.9 builds.
(In reply to comment #13) > zh-CN Ready for staging. > tested with 7.9 builds. Sorry,it's 7.8 builds.
fr-FR ready for staging
zh-TW ready for staging (Traditional Chinese)
(In reply to comment #16) > zh-TW ready for staging (Traditional Chinese) one more comment, please user builds after Jul/10.
pl-PL ready for staging (tested Jul 9 builds)
pt-PT ready for staging
he-IL ready for staging. the original builds from the Ftp don't include an RTL theme. the RTL compatible files can be found here: http://www.viewpoints.co.il/firefox/1.0.5/ can you please upload them?
(In reply to comment #20) > he-IL ready for staging. the tested builds are from 7.9
ca-AD ready for staging (tested 9 July builds)
eu-ES ready for staging (tested builds Jul/10)
af-ZA ready for staging
nl-NL ready for staging
pt-BR ready for staging
es-AR ready for staging As usual, Mac builds couldn't be tested but should work ok.
ja-JP/ja-JP-mac ready for staging. # tested with July 07,08,09,10,11 builds for win/linux, # tested with July 07,08,11 builds for mac And here are re-packaged win installers. # see bug 266309 (fixed only for trunk) http://ftp-developer.mozilla-japan.org/pub/mozilla-japan/firefox/development/1.0.5/ firefox-1.0.5-2005071119.ja-JP.win32.installer.exe is based on the build whose buildid=2005071119 as it's filename indicates. If you treat 20050710 or older builds as final, use other file in the same directory.
de-DE ready for staging
es-ES ready for staging (As es-AR, mac builds couldn't be tested but should work ok.)
en-GB ready for staging. As usual, Mac builds couldn't be tested but should be OK.
da-DK is also ready....we haven't been able to test Mac this time, but Win and Lin are tested and good to go.
All, Please keep adding status of your builds in this bug. We're currently evaluating the feedback we're getting on the en-US builds and seeing if they will affect the localizations. That's why you're not seeing localized builds on the web site just yet. We will know more tomorrow 7/14 at 12:00PM PST and will keep you posted. -Rafael
pa-IN ready for staging for Windows/Linux (for mac pa-IN couldn't be tested but it should work ok)
ga-IE ready for staging.
ko-KR is ready for staging.
On behalf of Michele Dal corso (it-IT owner): it-IT all OS are ready for staging
(In reply to comment #33) > Please keep adding status of your builds in this bug. We're currently > evaluating the feedback we're getting on the en-US builds and seeing if they > will affect the localizations. That's why you're not seeing localized builds on > the web site just yet. > > We will know more tomorrow 7/14 at 12:00PM PST and will keep you posted. Rafael, I must say that this new policy is very destructive for our local markets. We're more than 2 days after 1.0.5 release and l10n builds still are not released. We gather very bad press, we're blamed by users, we have no reason to explain this, we don't know how to explain this to journalists who're asking about this issue. We moved to centralized localization system to make l10n release easier and more stable. Such changes makes it absolutely pointless because we would be able to provide localized build by ourselves MUCH faster. Tens of milions of users are still using 1.0.4 while critical, security bugs are already published after en-US 1.0.5 release. I want to say that this seems to be absolutely ignored by Mozilla Foundation and by such delays you waste huge amount of work l10n teams are doing to promote our brands on local markets.
I would like to sign myself bellow Gandalf's post. (sorry for "me too" post)
(In reply to comment #33) > We will know more tomorrow 7/14 at 12:00PM PST and will keep you posted. Now it's 7/15 and we still know nothing, except from "something is wrong"...
Unconfirmed: In Firefox 1.0.5 was accidentaly changed some stable API, what caused problems with third-party extensions. Guys in MoFo are searching solution (and don't communicate).
How can we explain to the community and press what's going on? 1.0.6 is coming soon?
Please, stop being so vague! Just tell us what the problem is! Is the API change (the one Asa wrote about in npm.l10n as a problem with _Thunderbird_ 1.0.5) the problem here? If not, what is? And when can we expect the localized builds to finally show up? Or will we have a 1.0.6 release of Firefox? We are getting lots of e-mails from Firefox users in Poland asking us about why isn't Firefox 1.0.5 available in Polish (and we, the l10n team, are being blamed for the delay). The journalists are also asking us the same questions (and how can we answer those questions? "Mozilla.org has some problems, we will release the localized version >>when it's ready<<"?!). A few days more and it's gonna be a big PR disaster for Firefox outside the USA.
If I read Asa's post and comment in his own blog right, there _is_ going to be a Firefox 1.0.6 very soon and I assume that this is also the reason for the delay here, or better: The reason for the localized 1.0.5 builds not being released at all. Correct me if I am wrong.
That is corre(In reply to comment #44) > If I read Asa's post and comment in his own blog right, there _is_ going to be a > Firefox 1.0.6 very soon and I assume that this is also the reason for the delay > here, or better: The reason for the localized 1.0.5 builds not being released at > all. > > Correct me if I am wrong. You are correct. We received feedback on 1.0.5 from distributors and extension developers on API changes that affected them (not a security issue), so we're looking at a 1.0.6 to fix it. We will have builds of a 1.0.6 to test tomorrow morning and will hope to complete certification by Monday. We will provide status in this bug. If you have issues with the press or users regarding delays please email firstname.lastname@example.org or me and we can help.
> If you have issues with the press or users regarding delays please email email@example.com or me and we can help Yes. Please, can we ask for press release? Even small one? The one we could point out to anyone asking about l10n 1.0.5? - even a note on Mozilla Quality weblog would be enough. Something we could point out to anyone asking for explanation. And I hope that with 1.0.6 you will not release 1.0.6 en-US first, wait for feedback and THEN l10n builds. We strongly prefer to have the very same build as en-US have.
We're planning to count the Firefox 1.0.5 signoffs for Firefox 1.0.6. The 1.0.6 candidate l10n builds (from 2005-07-16 or 2005-07-17) should appear in http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/aviary1.0.1-l10n-candidates/ shortly. Testing these builds is a good idea even if you've already signed off on the 1.0.5 builds, and if you haven't yet signed off on the builds, it's probably better to sign off based on the 1.0.6 candidates.
Summary: ship Firefox 1.0.5 l10n builds → ship Firefox 1.0.5/1.0.6 l10n builds
We do need the repackaged ja-JP installers, though.
Er, actually, it looks like http://ftp-developer.mozilla-japan.org/pub/mozilla-japan/firefox/development/1.0.6/ has one.
Can anyone point me to a mention from Asai that the build in the 1.0.6 directory on ftp-developer.mozilla-japan.org is based on the Saturday morning Fx build?
(In reply to comment #51) > Can anyone point me to a mention from Asai that the build in the 1.0.6 directory > on ftp-developer.mozilla-japan.org is based on the Saturday morning Fx build? I'm getting my wires crossed. It looks to be based on the ja-JP build in the aviary1.0.1-l10n-candidates directory (which if true is correct). I would just like to hear from Asai that http://ftp-developer.mozilla-japan.org/pub/mozilla-japan/firefox/development/1.0.6/firefox-1.0.6-2005071718.ja-JP.win32.installer.exe is the build they want us to include in the relese.
Please, may you update Catalan (ca-AD) in http://www.mozilla.org/products/firefox/all.html? Is it necessary to sign again in another bug?
We had just finished our QA and no regression found. Thanks picking up my repackaged build. (the build is correct one) The build is based on build in aviary1.0.1-l10n-candidates dir. # the dir pointed by David Baron in comment #48 As the file name indicates, 2005-07-17 builds. Thanks finding the build, David and thanks shipping, Chase.
sq-AL ready for staging
(In reply to comment #20) > he-IL ready for staging. > > the original builds from the Ftp don't include an RTL theme. the RTL compatible > files can be found here: > > http://www.viewpoints.co.il/firefox/1.0.5/ i updated the builds to 1.0.6. the updated files can be found here: http://www.viewpoints.co.il/firefox/1.0.6/ can you please upload them?
mk-MK ready for staging (tested the Linux and Windows 1.0.6 builds)
sv-SE ready for staging
ga-IE ready for staging. (1.0.6 builds)
Made ca-AD, sq-AL, mk-MK, sv-SE, and he-IL live.
Regarding the pa-IN build (there's probably a better place to discuss this...), I'm not sure if it's had the necessary tests that we do before shipping a localization for the first time at http://wiki.mozilla.org/MozillaQualityAssurance:l10n_checklist . Furthermore, in some brief testing that I did, it seems the default bookmarks file doesn't work correctly (maybe some sort of parsing problem?) Regarding ast-ES -- nobody's signed off on that one.
ast-ES ready for staging
(In reply to comment #62) > ast-ES ready for staging ast-ES is now live.
Mass reassign of open bugs for firstname.lastname@example.org to email@example.com.
Assignee: chase → build
Status: ASSIGNED → NEW
Anything preventing us from closing this bug?
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.