Thanks Stefan, for your work, I will take a look. I appreciate your efforts
here and for getting these done before 3.3.1 :)

Regards,
Rahul Vats



On Sun, 26 Jul 2026 at 10:43, Stefan Wang <[email protected]> wrote:

> Hi Rahul and Airflowers:
>
> I had some time this week so took my first shot at translation for airflow
> (for the zh-CN locale).
>
> Three small PRs
> • common.json: https://github.com/apache/airflow/pull/70417
> • dashboard + HITL: https://github.com/apache/airflow/pull/70418
> • dags, components, admin: https://github.com/apache/airflow/pull/70419
>
> They fill in the rest of the zh-CN gaps, and I think it gets this locale
> to 100% on v3-3-test (completeness check script comes back clean).
>
> Would be happy to work with the community to get those reviewed for 3.3 RC.
>
> Thanks,
> Stefan
>
> > On Jul 24, 2026, at 4:21 AM, Rahul Vats <[email protected]> wrote:
> >
> > Hey fellow Airflowers,
> >
> > I'm sending this reminder on behalf of the release managers.
> > We plan to cut the Airflow 3.3.1 RC soon/by 3rd Aug 2026 from v3-3-test.
> >
> > After running the i18n completeness script against the v3-3-test branch,
> > here is the current coverage across merged locales as of 24th July 2026:
> >
> > Language   Coverage
> > --------   --------
> > ar         91.5%
> > ca         92.8%
> > de         93.2%
> > el          67.8%
> > es         95.5%
> > fr           87.9%
> > he         89.8%
> > hi          94.3%
> > hu         90.0%
> > it           70.0%
> > ja          72.2%
> > ko         94.3%
> > nl          95.4%
> > pl          91.0%
> > pt          80.5%
> > ru          79.3%
> > th          67.7%
> > tr           89.5%
> > zh-CN    92.7%
> > zh-TW    99.7%
> > --------   --------
> > Median     90.5%
> >
> > Translation owners and engaged translators are kindly asked to add
> missing
> > phrases in the v3-3-test branch ahead of the RC.
> >
> > Notes:
> > 1. Changes merged after the final patch release won't be included, and
> > missing terms will fall back to English.
> > 2. Please coordinate via the #i18n Slack channel if you need assistance
> or
> > expect terminology changes.
> > 3. Keep PRs small and focused to minimize review time on the patch
> branch.
> >
> > Thanks for your cooperation!
> > Rahul Vats
>
>

Reply via email to