1829418 - Apply content feedback to translations before Fx115 string freeze

Status: RESOLVED FIXED

(Firefox :: Translations, task)

Description

[Greg Tatum [:gregtatum]]

This bug will serve as a place to collect strings that need content feedback. These will be for things like error messages or accessibility labels that didn't come up during the design process.

Comment 1

[Francesco Lodolo [:flod]]

Why are there two bugs on file, one with 114 (bug 1829416) and this? Also, this targets version 114 in the categories section, 115 in the title.

We should have one bug to finalize the content before exposing for localization, and we should have time to do the actual localization, especially considering the target of this feature. If the review work hasn't started yet, I'm not sure targeting anything before 115 is realistic.

Comment 2

[Greg Tatum [:gregtatum]]

115 is early beta, and not going out to release. I filed the 114 bug to make sure we had a check-in point to get content review. I'll keep this one only. Can you provide a deadline for having final strings given a 115 early beta release, and 116 ship? I would prefer to keep two bugs. This one for collecting content feedback and Bug 1821038 for actually moving the .ftl files out of preview.

Comment 3

[Francesco Lodolo [:flod]]

The latest to target 115 is June 2nd (string freeze for the nightly cycle). The sooner we land content, the better are the chances that the content will be localized.

Then you would have another cycle (up to June 30th) to iterate over this content.

Comment 4

[Greg Tatum [:gregtatum]]

We should make sure and give content time to do QA on the strings, which means getting it into their hands by the week of May 22nd, which will give us time to apply any final feedback.

Comment 5

[Greg Tatum [:gregtatum]]

For what it's worth, I've been sharing progress pretty steadily to get feedback, but will keep this bug open for tracking next week.