1,035
edits
L10n:Official Localized Releases: Difference between revisions
→Official Localization
m (L10n:Localization Process End moved to L10n:Official Localized Releases: matches better with the content) |
|||
| Line 1: | Line 1: | ||
= Official Localization = | = Official Localization = | ||
A localized official release means that: | A localized official release means that: | ||
# Mozilla creates minor updates from CVS together with the en-US minor releases. [[L10n:Localization Process End#Minor Updates| | # Mozilla creates minor updates from CVS together with the en-US minor releases. [[L10n:Localization Process End#Minor Updates|Details...]] | ||
# Major upgrades, i.e., the shift from Firefox 2 to Firefox 3, is done through contributions of the localization teams. [[L10n:Localization Process End#Major Upgrades| | # Major upgrades, i.e., the shift from Firefox 2 to Firefox 3, is done through contributions of the localization teams. [[L10n:Localization Process End#Major Upgrades|Details...]] | ||
# The local team strengthens and enlarges the community. [[L10n:Localization Process End#Community Building| | # The local team strengthens and enlarges the community. [[L10n:Localization Process End#Community Building|Details...]] | ||
Following is more detail... | |||
== Minor Updates == | == Minor Updates == | ||
Mozilla Corporation resources handle minor updates, etc and collaborates with you to complete a release. Minor updates are generated from a stable branch, | Mozilla Corporation resources handle minor updates, etc and collaborates with you to complete a release. Minor updates are generated from a stable branch, this means, changes to that branch require approval and are tightly controlled on testing. This helps us to make sure that there are no regressions in minor updates. The corresponding tree rules are mentioned on the [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n l10n branch tinderbox] and announced in the .l10n newsgroup. All changes are documented in bugs, filed by the localizer in their Bugzilla component. | ||
More specifically, | More specifically, | ||
| Line 17: | Line 17: | ||
== Major Upgrades == | == Major Upgrades == | ||
Major updates are done by you. Our next major update is [http://wiki.mozilla.org/Firefox3 Firefox 3] | Major updates are done by you. Our next major update is [http://wiki.mozilla.org/Firefox3 Firefox 3] | ||
* | * There are some [http://developer.mozilla.org/en/docs/Create_a_new_localization#Following_your_localization tools] that are likely useful for you in this stage. | ||
* | * On the occasions when you don't meet the ship deadlines, we try to do everything we can to support you to meet the release dates. We do this by communicating well in advance of deadlines and being clear about module owners and the like. In the case where a deadline is going to be missed, we've considered these as our suggested options: | ||
* next release as acceptable | * next release as acceptable | ||
* special cases we may create a delay on being official build status | * special cases we may create a delay on being official build status | ||
Mozilla supports the [[Firefox:2.0_QA_Activities:L10n_Test_Plan|quality assurance]] testing of your build | Mozilla supports the [[Firefox:2.0_QA_Activities:L10n_Test_Plan|quality assurance]] testing of your build | ||
* We're improving automated testing and procedures for human testing to better support | * We're improving our automated testing capabilities and our procedures for human testing, to better support you for Firefox 3 | ||
* | * For major upgrades (Firefox 3), we've created a 2-week string freeze before the code freeze of the last Beta to ensure you have sufficient time to implement new changes | ||
* And, we've created new tools | * And, we've created new testing tools to provide nightly builds for which you can test your work against and have more dynamic results | ||
== Community Building == | == Community Building == | ||