Closed
Bug 302358
Opened 19 years ago
Closed 19 years ago
No Firefox 1.0.6 update for localised builds
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 302579
People
(Reporter: pascalc, Unassigned)
Details
(Keywords: intl)
Firefox 1.0.6 was released 10 days ago and so far, no localised builds are available through the automatic update mechanism. In https://update.mozilla.org/update/firefox/ only the en-US file was updated, all other locale files send 1.0.4 as the latest version. nb-NO even proposes 1.0.1 and ro-RO 1.0.2(!) (romanian and norwegian localisers had validated their rdf update file in the 1.0.4 l10 update tracking bug 293824). I can see a new PR disaster coming, users are starting to complain about it in European blogs and forums, it won't be long before some journalist picks it up and write a nice article about our security process and how Mozilla is unable to provide security updates to their users...
Comment 1•19 years ago
|
||
obviously those (most) builds are available ! http://www.mozilla.org/products/firefox/all
| Reporter | ||
Comment 2•19 years ago
|
||
yes peter, but not available through the update mechanism for current firefox users.
Updated•19 years ago
|
Component: Software Update → Build Config
QA Contact: software.update → build.config
Comment 3•19 years ago
|
||
I would have to agree with Pascual. In that period of time I've used Firefox nb-NO, it hasn't proposed a single automatic upgrade, though both 1.0.4 and 1.0.6 is out. Mozilla Norge has noted this bug, and will look at it when vacation is over.
Comment 4•19 years ago
|
||
We haven't completed putting the update files together. I hope to have them ready later today or Friday. When the update is ready, we'll be ready for sign-offs.
Comment 6•19 years ago
|
||
*** This bug has been marked as a duplicate of 302579 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Component: Build Config → Software Update
Resolution: --- → DUPLICATE
| Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•