Account confirmers, canmove, Confirmed users
2,357
edits
L10n:Becoming an Official Localization: Difference between revisions
Jump to navigation
Jump to search
L10n:Becoming an Official Localization (view source)
Revision as of 21:46, 18 May 2012
, 18 May 2012no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
__NOTOC__{{draft}}{{L10navbar}}<p><br> | __NOTOC__{{draft}}{{L10navbar}}<p><br> | ||
Releasing a localized Mozilla product is the ultimate goal for each L10n team. It is the culmination of all of their hard work and truly cause for celebrating! Each team has the option of releasing their work as either an official language pack or an official build. | |||
There are many advantages to releasing as an official build. This gives the L10n team's users the following: | |||
* a download link on for all three major platforms in each release channel | * a download link on for all three major platforms in each release channel | ||
* a localized install experience, including profile migration | * a localized install experience, including profile migration | ||
| Line 12: | Line 12: | ||
* localized web services experience (e.g., search, RSS Readers, RSS Feed/Live Bookmark and content handlers). | * localized web services experience (e.g., search, RSS Readers, RSS Feed/Live Bookmark and content handlers). | ||
[http://mozilla.github.com/process-releases/draft/development_overview/ Mozilla's rapid release cycle] gives L10n teams six weeks to localize the latest version of Firefox and other products before they are officially released. Each release channel represents a different stage of development and thus requires a different type of work for each L10n team. Once a team's work has been approved for inclusion in these release channels, it is critical for the teams to continue to localize and fix bugs in the appropriate channels for each release. | [http://mozilla.github.com/process-releases/draft/development_overview/ Mozilla's rapid release cycle] gives L10n teams six weeks to localize the latest version of Firefox and other products before they are officially released. Each release channel represents a different stage of development and thus requires a different type of work for each L10n team. Once a team's work has been approved for inclusion in these release channels, it is critical for the teams to continue to localize and fix bugs in the appropriate channels for each release. Whether a team choses to release as a language pack or as a build, they all have to kick off their releases on the train. | ||
=The release train= | =The release train= | ||