Closed Bug 302579 (fx106l10n-update) Opened 19 years ago Closed 19 years ago

Firefox 1.0.6 l10n update verifications

Categories

(Toolkit :: Application Update, defect)

Product:
Toolkit
Component:
Application Update
Version:
1.7 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: asa, Unassigned)

References

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, Firefox 1.0.1, Firefox 1.0.2, 1.0.3, and Firefox 1.0.4 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.6 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.6.

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.6
         o 1.0.1 -> 1.0.6
         o 1.0.2 -> 1.0.6
         o 1.0.3 -> 1.0.6
         o 1.0.4 -> 1.0.6


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.6
         o 1.0.1 -> 1.0.6
         o 1.0.2 -> 1.0.6
         o 1.0.3 -> 1.0.6
         o 1.0.4 -> 1.0.6

to verify that the live .rdf files are working as well.  If you have any
questions, please post them in this bug.  Thanks.
Alias: fx106l10n-update
Status: NEW → ASSIGNED
Component: General → Software Update
Alias: fx106l10n-update → fx105l10n-update
Alias: fx105l10n-update → fx106l10n-update
Adding the firefoxl10n watcher to CC.
nl-NL
1.0   -> 1.0.6 - OK
1.0.1 -> 1.0.6 - OK
1.0.2 -> 1.0.6 - OK
1.0.3 -> 1.0.6 - OK
1.0.4 -> 1.0.6 - OK
1.0.5 -> 1.0.6 - OK (for those who installed the pre-release version)
cs-CZ tested
1.0/1.0.x -> 1.0.6 OK
pl-PL - all updates OK
1.0   -> 1.0.6 - OK
1.0.1 -> 1.0.6 - OK
1.0.2 -> 1.0.6 - OK
1.0.3 -> 1.0.6 - OK
1.0.4 -> 1.0.6 - OK


ru-RU tested  - all updates OK
1.0   -> 1.0.6 - OK
1.0.1 -> 1.0.6 - OK
1.0.2 -> 1.0.6 - OK
1.0.3 -> 1.0.6 - OK
1.0.4 -> 1.0.6 - OK
nl-NL, cs-CZ, pl-PL, and ru-RU updates made live.  Needs ~1h to propagate.
1.0   -> 1.0.6 - OK
1.0.1 -> 1.0.6 - OK
1.0.2 -> 1.0.6 - OK
1.0.3 -> 1.0.6 - OK
1.0.4 -> 1.0.6 - OK
1.0.5 -> 1.0.6 - OK (I've had that one installed)

But Chase, would you mind telling us, why it took almost 10 days to set up this
bug and why no one responded to our qustions in the NG? I can absolutely
understand if you have to make things ready for this update, but why oh why
don't you communicate?
Our Users were vulnerable to a security exploit for more than 2 weeks (including
the 1.0.5 problem) with no auto update available. I had no idea what to answer
them when they asked me about the update. This procedure really has to change.
Uh, that was de-DE, sorry for bugspam.
Live pl-PL updates verified for all upgrade paths.

I'd also like to sign myself below Abdulkadir's questions.
fr-FR - all updates OK
1.0   -> 1.0.6 - OK
1.0.1 -> 1.0.6 - OK
1.0.2 -> 1.0.6 - OK
1.0.3 -> 1.0.6 - OK
1.0.4 -> 1.0.6 - OK
sv-SE works OK for all versions:

1.0 -> 1.0.6
1.0.1 -> 1.0.6
1.0.2 -> 1.0.6
1.0.3 -> 1.0.6
1.0.4 -> 1.0.6
Live ru-RU updates verified for all upgrade paths.
ca-AD works OK for all versions:

1.0 -> 1.0.6
1.0.1 -> 1.0.6
1.0.2 -> 1.0.6
1.0.3 -> 1.0.6
1.0.4 -> 1.0.6
All paths are OK for tr-TR (Turkish).

I experienced famous bug 268560 as usual at all paths excluding 1.0.1 to 1.0.6.
eu-ES tested - all updates OK
1.0   -> 1.0.6 - OK
1.0.1 -> 1.0.6 - OK
1.0.2 -> 1.0.6 - OK
1.0.3 -> 1.0.6 - OK
1.0.4 -> 1.0.6 - OK
zh-TW works OK for all versions:
1.0   -> 1.0.6 - OK
1.0.1 -> 1.0.6 - OK
1.0.2 -> 1.0.6 - OK
1.0.3 -> 1.0.6 - OK
1.0.4 -> 1.0.6 - OK
it-IT - all updates OK
1.0   -> 1.0.6 - OK
1.0.1 -> 1.0.6 - OK
1.0.2 -> 1.0.6 - OK
1.0.3 -> 1.0.6 - OK
1.0.4 -> 1.0.6 - OK
zh-CN update works fine.

1.0   -> 1.0.6 - OK
1.0.1 -> 1.0.6 - OK
1.0.3 -> 1.0.6 - OK
1.0.4 -> 1.0.6 - OK

no 1.0.2, 1.0.5 zh-CN released.
en-GB - some problems with 
https://aus.mozilla.org/update/firefox/test/en-GB.rdf

1.0   -> 1.0.6 OK
1.0.1 -> 1.0.6 OK
1.0.2 -> 1.0.6 OK
1.0.3 -> 1.0.6 OK
1.0.4: Clicking "Check Now" button checks, then responds with "Firefox was not
able to find any available updates".  Testing on a brand new profile gives the
same results.

en-GB and ga-IE seem to have malformed AB-CD.rdf. They offer updates in the
"header" but have no "data block" for versions 1.0.4 and 1.0.5.

Also, test/pa-IN is missing. Users manually checking for updates will get an
empty list of possible updates (bug 290550).
de-DE, fr-FR, sv-SE, ca-AD, tr-TR, eu-ES, zh-TW, it-IT, and zh-CN updates made
live.  Needs ~1h to propagate.

(In reply to comment #19)
> en-GB - some problems with 
> https://aus.mozilla.org/update/firefox/test/en-GB.rdf

and

(In reply to comment #20)
> en-GB and ga-IE seem to have malformed AB-CD.rdf. They offer updates in the
> "header" but have no "data block" for versions 1.0.4 and 1.0.5.

Good catch guys -- this is why we test. :)  I've fixed both of these RDF files
to have updates listed for 1.0.4 and 1.0.5.

> Also, test/pa-IN is missing. Users manually checking for updates will get an
> empty list of possible updates (bug 290550).

I created pa-IN.rdf from en-US.rdf.  Thanks.
ja-JP update works fine.

1.0   -> 1.0.6 - OK
1.0.1 -> 1.0.6 - OK
1.0.2 -> 1.0.6 - OK
1.0.3 -> 1.0.6 - OK
1.0.4 -> 1.0.6 - OK

All versions are tested on WinXP/2K/98SE
Sorry, ja-JP tested on WinXP/2K/ME, not WinXP/2K/98SE
Update from all versions works fine.
(In reply to comment #21)
> (In reply to comment #19)
> > en-GB - some problems with 
> 
> Good catch guys -- this is why we test. :)  I've fixed both of these RDF files
> to have updates listed for 1.0.4 and 1.0.5.

Thanks. I've re-tested the following paths for en-GB:

1.0   -> 1.0.6 still OK
1.0.1 -> 1.0.6 still OK
1.0.2 -> 1.0.6 still OK
1.0.3 -> 1.0.6 still OK
1.0.4 -> 1.0.6 now OK

and tested

1.0.5 -> 1.0.6 OK


For anyone interested in how far the verification process has progressed (over
all the locales) I have knocked up some scripts that poll the "production"
update RDFs:

http://wiki.mozilla.org/L10n:Firefox_1.0.x_Application_Update

This page provides information only, and isn't intended to distract anyone from
the this bug.

fi-FI - all updates OK
1.0   -> 1.0.6 - OK
1.0.1 -> 1.0.6 - OK
1.0.2 -> 1.0.6 - OK
1.0.3 -> 1.0.6 - OK
1.0.4 -> 1.0.6 - OK
sl-SI OK
pt-PT OK
es-AR OK
Sorry for the delay.
verified that the live .rdf files for nl-NL are ok
nb-NO OK
Chase, locale owners have reported that these locales are ready to go live:
ja-JP, en-GB, fi-FI, sl-SI, pt-PT, es-AR, nb-NO
de-DE: all live paths are okay.
(In reply to comment #32)
> Chase, locale owners have reported that these locales are ready to go live:
> ja-JP, en-GB, fi-FI, sl-SI, pt-PT, es-AR, nb-NO

Thanks Nick.  Updates for these locales have been made live.
[CC'ing owners of the outstanding locales]

To owners of af-ZA, ast-ES, da-DK, el-GR, es-ES, ga-IE, he-IL, hu-HU, ko-KR,
mk-MK, pt-BR, ro-RO, sq-AL:

This bug describes the steps for mozilla.org to provide update notifications for
localised Firefox 1.0.6. Please read the first post for full information, but
note that comments about staging and builds being marked * and ? no longer apply
because all locale installers are on the mirrors by now.

One way to be kept informed about future l10n bugs is to configure your Bugzilla
preferences to watch firefoxl10n@hotmail.com (go to bottom of a Bugzilla page,
then Prefs, Email Settings, Users to watch, paste in the email address, click
the Submit button). This address is CC'd to relevant bugs soon after they are filed.
mk-MK
  1.0.2 -> 1.0.6 ok
  1.0.3 -> 1.0.6 ok
  1.0.4 -> 1.0.6 ok
ga-IE
  1.0.1 -> 1.0.6 OK
  1.0.2 -> 1.0.6 OK
  1.0.3 -> 1.0.6 OK
  1.0.4 -> 1.0.6 OK

There was no 1.0 ga-IE release.
pt-BR update works fine.
ro-RO OK. Tested {1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4} -> 1.0.6
https://aus.mozilla.org/update/firefox/test/ko-KR.rdf has some problem on
malformed format. Sorry for delay.
channy, the test ko-KR.rdf seems to be OK when compared to the en-US file. Could
you be more specific about how the file is malformed and what behavior you see ? 

Note that trunk and Mozilla1.8 builds of Firefox (and probably SeaMonkey/Suite)
report a "XML parsing error" if you try to load the rdf in a browser tab, rather
than setting the app.update.url preference using about:config.


da-DK - all updates OK  (tested on Windows XP)
1.0   -> 1.0.6 - OK
1.0.1 -> 1.0.6 - OK
1.0.2 -> 1.0.6 - OK
1.0.3 -> 1.0.6 - OK
1.0.4 -> 1.0.6 - OK

For Firefox 1.5 and onwards the locale code for danish will be "da" -- will this
fact affect the workings of the automatic update system ?
*** Bug 302358 has been marked as a duplicate of this bug. ***
QA Contact: general → software.update
Mass reassign of open bugs for chase@mozilla.org to build@mozilla-org.bugs.
Assignee: chase → build
Status: ASSIGNED → NEW
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
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.