Closed
Bug 309660
(fx107l10n-update)
Opened 20 years ago
Closed 19 years ago
Firefox 1.0.7 l10n update verifications
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: chase, Unassigned)
References
Details
Attachments
(1 file)
|
73.98 KB,
image/png
|
Details |
Localization Release Tasks for Application Update
All of the builds that you sign off on will be staged out to all of our mirrors.
This mirroring out process can take as much as 24 hours (time for all of our
mirrors to get the builds). Keep an eye on this bug to see if your locale is
staged and ready for testing.
In order to make each of the localizations available via Application Update, we
need your help to test the update mechanism. For those builds that are already
available on all of our mirrors, this should be able to be completed quickly.
For those builds that haven't all mirrored out, it could be up to 24 hours
before this testing can be completed.
To test the update mechanism, you need to install each of Windows Firefox 1.0
through 1.0.6 and follow these steps for each of those builds:
1. Type about:config in the address bar and hit enter.
2. Locate and change the app.update.url string to the .rdf URL listed
below.
3. Restart and go to Tools -> Options and select the Advanced panel.
4. Locate and press the Check Now for updates button.
At this point, you should be notified that the 1.0.7 update is
available.
5. Proceed to download and install.
6. At the end of the install, start Firefox and select the Help -> About
Mozilla Firefox menu item to verify that you are running version
1.0.7.
If all of this is successful, please add a comment to this bug informing us of
that and we will update the live RDF file which will notify all users of your
locale that an update is available.
If the update fails and you are testing one of the builds below marked with a *,
please repeat the test and if it still fails, please report that failure to this
thread. Be sure to included the steps you took above and where in those steps
the install failed as well as how it failed. Likely failures will be a "hang"
between step 4 and step 5. If your update is successful, please add a comment to
this bug informing us of that and we will update the live RDF file which will
notify all users of your locale that an update is available.
If the update fails and you are testing one of the builds marked with a ?,
please wait and try again in several hours. If it is still failing in 24 hours,
please report that failure to this bug. Your builds may not have made it to all
the mirrors yet and that could cause the failure (between step 4 and step 5.) so
do not report a failure until the build will have had a chance to mirror out to
all of the servers.
Here are the quick checklist for this set of tests:
o The about:config preference name is 'app.update.url'.
o The URL to chance it to is in the format of
https://aus.mozilla.org/update/firefox/test/<L10N>.rdf
and each one of these is listed below
o Only test Windows platforms. Other platforms will show no
updates.
o Use as an example en-US update as a baseline to set expectations
for how the update should function. Your update should work just
like en-US.
o Verify each of these update paths.
o 1.0 -> 1.0.7
o 1.0.1 -> 1.0.7
o 1.0.2 -> 1.0.7
o 1.0.3 -> 1.0.7
o 1.0.4 -> 1.0.7
o 1.0.5 -> 1.0.7
o 1.0.6 -> 1.0.7
Additionally, once you have verified the test .rdf URLs are working and we make
your locale live, you will need to retest using the default .rdf URL:
https://aus.mozilla.org/update/firefox/<l10N>.rdf
for these upgrade paths:
o 1.0 -> 1.0.7
o 1.0.1 -> 1.0.7
o 1.0.2 -> 1.0.7
o 1.0.3 -> 1.0.7
o 1.0.4 -> 1.0.7
o 1.0.5 -> 1.0.7
o 1.0.6 -> 1.0.7
to verify that the live .rdf files are working as well. If you have any
questions, please post them in this bug. Thanks.
| Reporter | ||
Updated•20 years ago
|
Alias: fx107l10n-update
| Reporter | ||
Comment 1•20 years ago
|
||
At this time, every 1.0.x test update RDF (those at
https://aus.mozilla.org/update/firefox/test/<L10N>.rdf) point to that locale's
1.0.7 version. However, only the following locales have a 1.0.7 update package
(and hence will be able to update properly):
af-ZA
ca-AD
cs-CZ
da-DK
de-DE
el-GR
en-GB
es-AR
eu-ES
fi-FI
fr-FR
hu-HU
it-IT
ja-JP
nb-NO
nl-NL
pl-PL
pt-PT
ru-RU
sl-SI
tr-TR
zh-CN
zh-TW
If your locale has a 1.0.7 candidate package and is not listed here, please see
bug 309375 in order to sign-off first on those packages.
Status: NEW → ASSIGNED
Comment 2•20 years ago
|
||
I've tried to update 1.0 -> 1.0.7. Update is found but when I tried to download
it, I've got error message (in Russian, I'm translated it back in English for
convenience):The following components could not be installed due to errors (the
file could not be downloaded, was corrupt, or for some other reason): Firefox
1.0.7 (ru-RU) software update (Not a valid install package)
| Reporter | ||
Comment 3•20 years ago
|
||
(In reply to comment #2)
> Created an attachment (id=197082) [edit]
> Error (ru-RU 1.0 -> 1.0.7)
>
> I've tried to update 1.0 -> 1.0.7. Update is found but when I tried to download
> it, I've got error message (in Russian, I'm translated it back in English for
> convenience):The following components could not be installed due to errors (the
> file could not be downloaded, was corrupt, or for some other reason): Firefox
> 1.0.7 (ru-RU) software update (Not a valid install package)
I didn't mark the listed locales with ? (overlooked that), but each of these
were just added to the FTP staging site within the past hour. Please give them
a little time to mirror out before trying again. If you continue to see the
problem, let me know via this bug and I'll take a look at the RDF file.
Comment 4•20 years ago
|
||
(In reply to comment #3)
> I didn't mark the listed locales with ? (overlooked that), but each of these
> were just added to the FTP staging site within the past hour. Please give them
> a little time to mirror out before trying again. If you continue to see the
> problem, let me know via this bug and I'll take a look at the RDF file.
Never mind. Just tried again and Firefox was updated successfully from 1.0 -> 1.0.7.
Comment 5•20 years ago
|
||
ru-RU tested - all updates OK
1.0 -> 1.0.7 - OK
1.0.1 -> 1.0.7 - OK
1.0.2 -> 1.0.7 - OK
1.0.3 -> 1.0.7 - OK
1.0.4 -> 1.0.7 - OK
1.0.5 -> 1.0.7 - OK
1.0.6 -> 1.0.7 - OK
Comment 6•20 years ago
|
||
All paths are OK for tr-TR (Turkish).
I experienced bug 268560 as usual at all paths.
Comment 7•20 years ago
|
||
Chase: af-ZA, mk-MK, sq-AL are missing
Comment 8•20 years ago
|
||
pl-PL - all update paths ok
1.0.6 -> 1.0.7 : ok
1.0.4 -> 1.0.7 : ok
1.0.3 -> 1.0.7 : ok
1.0.2 -> 1.0.7 : ok
1.0.1 -> 1.0.7 : ok
1.0 -> 1.0.7 : ok
(all tested under Win 98 SE, except from 1.0.1->1.0.7 on Win XP Pro)
Comment 9•20 years ago
|
||
de-DE all update paths tested and ok:
1.0 -> 1.0.7 OK
1.0.1 -> 1.0.7 OK
1.0.2 -> 1.0.7 OK
1.0.3 -> 1.0.7 OK
1.0.4 -> 1.0.7 OK
1.0.6 -> 1.0.7 OK
Comment 10•20 years ago
|
||
zh-CN all update paths tested and ok:
1.0 -> 1.0.7 OK
1.0.1 -> 1.0.7 OK
1.0.2 -> no zh-CN release
1.0.3 -> 1.0.7 OK
1.0.4 -> 1.0.7 OK
1.0.6 -> 1.0.7 OK
Comment 11•20 years ago
|
||
zh-TW all update paths tested and ok:
(all tested on Windows XP)
1.0 -> 1.0.7 OK
1.0.1 -> 1.0.7 OK
1.0.2 -> 1.0.7 OK
1.0.3 -> 1.0.7 OK
1.0.4 -> 1.0.7 OK
1.0.6 -> 1.0.7 OK
Comment 12•20 years ago
|
||
es-AR paths OK
o 1.0 -> 1.0.7 OK
o 1.0.1 -> 1.0.7 OK
o 1.0.2 -> 1.0.7 OK
o 1.0.3 -> 1.0.7 OK
o 1.0.4 -> 1.0.7 OK
o 1.0.5 -> 1.0.7 OK
o 1.0.6 -> 1.0.7 OK
Comment 13•20 years ago
|
||
nb-NO is ready.
Comment 14•20 years ago
|
||
ca-AD all update paths tested and ok (Windows XP Pro)
1.0 -> 1.0.7 OK
1.0.1 -> 1.0.7 OK
1.0.2 -> 1.0.7 OK
1.0.3 -> 1.0.7 OK
1.0.4 -> 1.0.7 OK
1.0.6 -> 1.0.7 OK
Comment 15•20 years ago
|
||
hu-HU all update paths tested and ok (Windows 2000)
1.0 -> 1.0.7 OK
1.0.1 -> 1.0.7 OK
1.0.2 -> 1.0.7 OK
1.0.3 -> 1.0.7 OK
1.0.4 -> 1.0.7 OK
1.0.6 -> 1.0.7 OK
Comment 16•20 years ago
|
||
fr-FR tested - all updates OK
1.0 -> 1.0.7 - OK
1.0.1 -> 1.0.7 - OK
1.0.2 -> 1.0.7 - OK
1.0.3 -> 1.0.7 - OK
1.0.4 -> 1.0.7 - OK
1.0.5 -> 1.0.7 - N/A
1.0.6 -> 1.0.7 - OK
Comment 17•20 years ago
|
||
ja-JP - all update paths are fine (on Win XP)
1.0 -> 1.0.7 OK
1.0.1 -> 1.0.7 OK
1.0.2 -> 1.0.7 OK
1.0.3 -> 1.0.7 OK
1.0.4 -> 1.0.7 OK
1.0.6 -> 1.0.7 OK
Comment 18•20 years ago
|
||
All updates for existing cs-CZ 1.0.x versions are OK.
Comment 19•20 years ago
|
||
it-IT tested - all updates OK
1.0 -> 1.0.7 - OK
1.0.1 -> 1.0.7 - OK
1.0.2 -> 1.0.7 - OK
1.0.3 -> 1.0.7 - OK
1.0.4 -> 1.0.7 - OK
1.0.5 -> 1.0.7 - Not available
1.0.6 -> 1.0.7 - OK
Comment 20•20 years ago
|
||
Greek (el-GR) - all updates OK
1.0 -> 1.0.7 - OK
1.0.1 -> 1.0.7 - OK
1.0.2 -> 1.0.7 - OK
1.0.3 -> 1.0.7 - OK
1.0.4 -> 1.0.7 - OK
1.0.6 -> 1.0.7 - OK
Comment 21•20 years ago
|
||
We have bug 309856, which reports that update switches from zh-TW to en-US, which
I can reproduce looking at the source. Of course, we don't uncover this when
setting the pref to testing :-(.
zh-TW not ready for update,
http://lxr.mozilla.org/l10n-aviarybranch/source/toolkit/locales/zh-TW/chrome/mozapps/update/update.properties#12
needed a fix.
| Reporter | ||
Comment 22•20 years ago
|
||
Made ru-RU, tr-TR, pl-PL, de-DE, zh-CN, es-AR, nb-NO, ca-AD, hu-HU, fr-FR,
ja-JP, cs-CZ, it-IT, and el-GR live.
Comment 23•20 years ago
|
||
sl-SI is OK
Comment 24•20 years ago
|
||
pt-PT is OK.
Comment 25•20 years ago
|
||
fi-FI all paths ok.
Comment 26•20 years ago
|
||
da-DK all paths verified OK...
Comment 27•20 years ago
|
||
pl-PL: all update paths verified OK.
Comment 28•20 years ago
|
||
nl-NL is ok (all paths)
Comment 29•20 years ago
|
||
eu-ES all update paths verified OK!
Comment 30•20 years ago
|
||
en-GB tested - all updates OK
1.0 -> 1.0.7 - OK
1.0.1 -> 1.0.7 - OK
1.0.2 -> 1.0.7 - OK
1.0.3 -> 1.0.7 - OK
1.0.4 -> 1.0.7 - OK
1.0.5 -> 1.0.7 - OK
1.0.6 -> 1.0.7 - OK
Comment 31•20 years ago
|
||
he-IL all paths OK.
| Reporter | ||
Comment 32•20 years ago
|
||
Made sl-SI, pt-PT, fi-FI, da-DK, nl-NL, eu-ES, en-GB, and he-IL live.
Comment 33•20 years ago
|
||
pt-BR: all update paths ok
Comment 34•20 years ago
|
||
sv-SE all versions to 1.0.7 tested ok.
| Reporter | ||
Comment 35•19 years ago
|
||
Mass reassign of open bugs for chase@mozilla.org to build@mozilla-org.bugs.
Assignee: chase → build
Status: ASSIGNED → NEW
Comment 36•19 years ago
|
||
No more releases are happening on the 1.0.x branch; looks like this is no longer needed anyway.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•