Open Bug 1960763 Opened 4 days ago Updated 3 days ago

Adjust ./mach newtab update-locales to also query Pontoon for the creation date of all strings

Categories

(Firefox :: New Tab Page, task, P3)

Product:
Firefox
Component:
New Tab Page
Type:
task

Tracking

()

People

(Reporter: mconley, Unassigned)

References

Details

(Whiteboard: [hnt-trainhop])

For strings that are missing, we want to know how long they've been available on Pontoon. I believe string keys that have been on the Beta channel for at least 3 weeks but haven't yet been translated qualify for falling back to the fallback locales (ultimately landing on en-US if no other appropriate fallbacks exist). Do I have that correct, bolsson?

Flags: needinfo?(bolsson)
Summary: Adjust ./mach update-locales to also query Pontoon for the creation date of all strings → Adjust ./mach newtab update-locales to also query Pontoon for the creation date of all strings

There's no way currently to get that information out of Pontoon. While the entry creation date is stored in the database, that information isn't exposed to any API (and while we are planning on working on Pontoon APIs at some point, that won't be happening until at least H2). We'll likely need to calculate based off of something else (perhaps tracking when strings land in mozilla-central).

In typical scenarios (e.g. standard Firefox strings) fallback happens automatically if a string doesn't exist for a locale. The user's language settings determine what languages strings fall back to, but ultimately en-US if nothing is found. Regarding timeline, while we normally ask for a full cycle typically, in case of these newtab off-train updates we'd want at least 3 weeks for localization to work on strings before we consider exposing them.

I'm not sure if this answers your questions mconley, if not can you clarify what you're asking?

Flags: needinfo?(bolsson)
You need to log in before you can comment on or make changes to this bug.