L20n in Gecko Landing Plan
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAAAB
1
MilestonesTarget DateFx ReleaseStatusBug IDMain ItemsPost MortemMain risks
2
Soft LaunchOctober 1, 201758COMPLETED1402061code landing, new langpacks12/01/2017
3
First MigrationJanuary 3, 201759COMPLETED1407256migration flow, pontoon FTL01/18/2018
4
PreferencesMarch 1, 201860/61COMPLETED141573006/06/2018Search Functionality, XBL removal
5
Open MigrationOctober 24, 201865COMPLETED1455649non-priv, system addons etc.09/06/2018problems aligning Fluent with edge cases in Firefox
6
Startup PathJuly 27, 201970COMPLETED1441035talos green--Performance
7
Full LaunchOctober 17, 201971COMPLETEDdocs, developer workflow11/?/2019full FTL support in the toolchain
8
9
10
11
Description
12
Soft LaunchIn this phase we intent to introduce a single, new, trivial message using Fluent into Firefox. That will require all core systems to work like LocaleService, Intl, L10nRegistry, Fluent, Fluent-DOM, and Fluent-Gecko. On top of that, we'll need compare-locales, and pontoon support. In this phase we will intentionally keep the new API under control with a whitelist of enabled .ftl files to remove the risk of engineers starting to use our API prematurely.
13
14
15
16
17
18
19
First MigrationIn this phase we will migrate the first piece of UI to Fluent. It will be a stable and fairly hidden piece of UI that is unlikely to change within months. We'll also want the strings involved to be as simple as possible. This phase will test our migration infrastructure in Fluent, Gecko and Pontoon.
20
21
22
23
24
25
PreferencesIn this phase, we will migrate a single, complex component off the start up path - Preferences. It'll require us to prove Fluent integration with Intl, and Pontoon handling of more complex FTL features. We will be closely working with the most senior Firefox Front-End Team engineers as reviewers and reacting to their feedback on missing and required features in Fluent.
26
27
28
29
30
31
Open MigrationIn this phase we will start migrating more pieces of Firefox front-end to Fluent one by one. All work will be tightly monitored by L10n Drivers team to allow us to evaluate readiness of our system for each component, postpone it if needed, and adjust the speed of transition on the go.
32
33
34
35
36
37
Startup PathIn this phase we expect to be ready to enable Fluent on the startup path of Firefox. This phase may happen at the same time as the previous one, but if we encounter delays, we can specifically postpone this one without blocking the previous one.
38
39
40
41
42
43
Full LaunchIn this phase we will remove the whitelist and let the developers start using the new API. We'll still monitor their work and will ask for a period of adding us as reviewers on any patch that uses the new API, until we gain confidence in the new system.
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...