Bug 290883 (fx103l10n-update)

Firefox 1.0.3 update verifications

RESOLVED FIXED

Status

()

RESOLVED FIXED
14 years ago
13 years ago

People

(Reporter: jay, Unassigned)

Tracking

1.0 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
Localization Release Tasks for Application Update

All of the builds that you signed off on are either already staged
out to all of our mirrors or in the process of staging out to the
mirrors. This mirroring out process can take as much as 24 hours (time
for all of our mirrors to get the builds).

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, and Firefox 1.0.2 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.3 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.3.

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.3
         o 1.0.1 -> 1.0.3
         o 1.0.2 -> 1.0.3

These builds were staged before Saturday evening and should be available
at all of the Mozilla mirrors. It is expected that these updates should
all succeed. Please let us know in a reply to this bug if any of these
fail. Please let us know in this bug if the update is successful.

   * https://aus.mozilla.org/update/firefox/test/eu-ES.rdf
   * https://aus.mozilla.org/update/firefox/test/fr-FR.rdf
   * https://aus.mozilla.org/update/firefox/test/hu-HU.rdf
   * https://aus.mozilla.org/update/firefox/test/it-IT.rdf
   * https://aus.mozilla.org/update/firefox/test/ja-JP.rdf
   * https://aus.mozilla.org/update/firefox/test/nb-NO.rdf
   * https://aus.mozilla.org/update/firefox/test/nl-NL.rdf
   * https://aus.mozilla.org/update/firefox/test/pl-PL.rdf
   * https://aus.mozilla.org/update/firefox/test/pt-BR.rdf
   * https://aus.mozilla.org/update/firefox/test/pt-PT.rdf
   * https://aus.mozilla.org/update/firefox/test/ro-RO.rdf
   * https://aus.mozilla.org/update/firefox/test/ru-RU.rdf
   * https://aus.mozilla.org/update/firefox/test/sl-SI.rdf
   * https://aus.mozilla.org/update/firefox/test/sv-SE.rdf

These builds were staged today and may not be available at all of the
Mozilla mirrors until tomorrow. If the update fails, please try again
several times over the next 24 hours. If the update is successful, then
report that with a comment to bug

   ? https://aus.mozilla.org/update/firefox/test/af-ZA.rdf
   ? https://aus.mozilla.org/update/firefox/test/ca-AD.rdf
   ? https://aus.mozilla.org/update/firefox/test/cs-CZ.rdf
   ? https://aus.mozilla.org/update/firefox/test/da-DK.rdf
   ? https://aus.mozilla.org/update/firefox/test/el-GR.rdf
   ? https://aus.mozilla.org/update/firefox/test/en-GB.rdf
   ? https://aus.mozilla.org/update/firefox/test/es-AR.rdf
   ? https://aus.mozilla.org/update/firefox/test/fi-FI.rdf
   ? https://aus.mozilla.org/update/firefox/test/ko-KR.rdf
   ? https://aus.mozilla.org/update/firefox/test/mk-MK.rdf
   ? https://aus.mozilla.org/update/firefox/test/tr-TR.rdf
   ? https://aus.mozilla.org/update/firefox/test/zh-CN.rdf
   ? https://aus.mozilla.org/update/firefox/test/zh-TW.rdf

Please make it easy for us to follow the feedback at the bug and in this post by
including the name of your locale at the beginning of the post. Thanks.
(Reporter)

Comment 1

14 years ago
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 the 3 upgrade paths: 

1.0 -> 1.0.3
1.0.1 -> 1.0.3
1.0.2 -> 1.0.3

to verify that the live .rdf files are working as well.  If you have any
questions, please post them in this bug.  Thanks.
it-IT is OK

After the update Firefox works fine, no duplicate voices in the Windows Control
Panel.
Verified each passage twice without errors:
1.0 (20041110 Firefox/1.0) -> 1.0.3 (20050414 Firefox/1.0.3)
1.0.1 (20050226 Firefox/1.0.1) -> 1.0.3 (20050414 Firefox/1.0.3)
1.0.2 (20050318 Firefox/1.0.2) -> 1.0.3 (20050414 Firefox/1.0.3)

Comment 3

14 years ago
ca-AD is OK.

Updates from 1.0, 1.0.1 and 1.0.2 to 1.0.3 work nice using
https://aus.mozilla.org/update/firefox/test/ca-AD.rdf

There are no duplicate icons in the Windows Control
Panel either.
(Reporter)

Updated

14 years ago
Assignee: jay → chase
(Reporter)

Updated

14 years ago
QA Contact: general → jay

Comment 4

14 years ago
sl-SI works fine

Comment 5

14 years ago
sv-SE is ok using the test .rdf.

Comment 6

14 years ago
zh-CN Application Update tested:
  1.0->1.0.3 not OK,I can only see an update message for 1.0.1 (zh-CN).
  1.0.1->1.0.3 OK.
  1.0.2->1.0.3 no 1.0.2 zh-CN released.skipping.

Comment 7

14 years ago
hu-HU is ok using the test .rdf.
zh-TW is ok (using the test .rdf)

Comment 9

14 years ago
fr-FR is ok
nl-NL is OK

1.0 (20041202 Firefox/1.0) -> 1.0.3 (20050414 Firefox/1.0.3)
1.0.1 (20050226 Firefox/1.0.1) -> 1.0.3 (20050414 Firefox/1.0.3)
1.0.2 (20050318 Firefox/1.0.2) -> 1.0.3 (20050414 Firefox/1.0.3)
Update test results for tr-TR (Turkish):

1.0 -> 1.0.3: Succesfully updated. See the note below.
1.0.1 -> 1.0.3: Succesfully updated.
1.0.2 -> 1.0.3: Succesfully updated. See the note below.

Note: At first lunch of updated Firefox, there was red update notification icon
at right-top of Firefox window. Clicked and checked for updates again. It didn't
find anything new, because it had already been updated to 1.0.3. The icon
disappered by the next (2nd) lunch.
fi-FI all update paths OK
ru-RU is OK (using the test .rdf).
pl-PL: all updates OK

Tested on Windows 98.

Comment 15

14 years ago
it-IT, ca-AD, sl-SI, sv-SE, hu-HU, zh-TW, fr-FR, nl-NL, tr-TR, fi-FI, ru-RU, and
pl-PL update made live.

Could zh-CN retest 1.0 -> 1.0.3?  I caught the problem in the RDF file and it
should be fixed now.
cs-CZ is OK

Comment 17

14 years ago
pt-PT is ok (test rdf).

However, I also saw the red update icon after running the updated Firefox (which
went away as soon as I checked for updates - there weren't any, obviously).

Comment 18

14 years ago
ko-KR is okay too.

Comment 19

14 years ago
es-AR working as expected.
Everything was OK.

Comment 20

14 years ago
(In reply to comment #15)
> Could zh-CN retest 1.0 -> 1.0.3?  I caught the problem in the RDF file and it
> should be fixed now.

At this time, 1.0 -> 1.0.3 is not OK yet. what I see in the test zh-CN.rdf is:
app:name="Firefox 1.0.1 (zh-CN) Software Update"
I think it shoud be
app:name="Firefox 1.0.3 (zh-CN) Software Update"

es-ES updates ok until 1.0.2. I know es-ES is not in the list, but I don't know
why if 1.0.2 is ok. Please update accordingly.

Comment 22

14 years ago
en-GB is OK

tested:
 1.0 --> 1.0.3
 1.0.1 --> 1.0.3
 1.0.2 --> 1.0.3

as with comment 11 and comment 17, the update icon appeared after a successful
update.  I didn't think to check whether it went away on its own (I clicked on
it each time, d'oh).

Updating 1.0.2 gave an error the first time (Not a valid install package), but
worked when I tried again.  I'm assuming this is a mirror not being up to date.

Comment 23

14 years ago
(In reply to comment #15)

> Could zh-CN retest 1.0 -> 1.0.3?  I caught the problem in the RDF file and it
> should be fixed now.

zh-CN is OK now:
  1.0->1.0.3 OK.
  1.0.1->1.0.3 OK.
  1.0.2->1.0.3 no 1.0.2 zh-CN released.skipping.

Comment 24

14 years ago
Can we expect the pt-PT rdf to become effective soon?

Comment 25

14 years ago
cs-CZ, pt-PT, ko-KR, es-AR, en-GB, and zh-CN update made live.

es-ES update can go live once the es-ES candidate is signed off on and made live
itself.  Please test the candidate in
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/aviary1.0.1-l10n-candidates/
and signal if the locale can be made live by adding a comment to bug fx103l10n.

Comment 26

14 years ago
pt-PT is ok (live RDF)

Comment 27

14 years ago
ja-JP is OK

tested:
 1.0 --> 1.0.3
 1.0.1 --> 1.0.3
 1.0.2 --> 1.0.3

Comment 28

14 years ago
pt-BR is OK.
Updates from 1.0, 1.0.1 and 1.0.2 work nice.
As Hidehiro Kozawa said, ja-JP update works fine.
Though red icon will remain after update, it will vanish after
checking for update again.
It's not fatal problem and OK to release.
# same as #11, #17, #22

I wrote this post to add info about this trivial problem and
ensure ja-JP is OK, in case you require locale owner's post.
# Kozawa is peer and he also have 1l0n cvs account.
# When I'm busy, he will do in behalf of me.

Comment 30

14 years ago
(In reply to comment #28)
> pt-BR is OK.
> Updates from 1.0, 1.0.1 and 1.0.2 work nice.


Is there something else I should do to get pt-BR update released?

Updated

14 years ago
Alias: fx103l10n-update

Comment 31

13 years ago
Mass reassign of open bugs for chase@mozilla.org to build@mozilla-org.bugs.
Assignee: chase → build
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.