2
edits
No edit summary |
|||
Line 13: | Line 13: | ||
Since after all, incremental security updates are not allowed to change anything major in the interface, and even if they do, the patch could be applied in en-US first (not localizing the new strings, but leaving the old ones intact) and when a language pack is available it will update the rest of the strings. | Since after all, incremental security updates are not allowed to change anything major in the interface, and even if they do, the patch could be applied in en-US first (not localizing the new strings, but leaving the old ones intact) and when a language pack is available it will update the rest of the strings. | ||
== Holizz's Comments == | === Holizz's Comments === | ||
:... if say, there's a minor security update coming up, users with locales other than en-US could apply the security fix without having to wait for a version of Firefox in their locale. | :... if say, there's a minor security update coming up, users with locales other than en-US could apply the security fix without having to wait for a version of Firefox in their locale. | ||
Isn't that's what happens already? I downloaded 1.5 beta 1 in en-GB. When I updated to 1.5 it was still en-GB despite the en-GB installer not being available until several weeks later. | Isn't that's what happens already? I downloaded 1.5 beta 1 in en-GB. When I updated to 1.5 it was still en-GB despite the en-GB installer not being available until several weeks later. |
edits