Hey again, Updating that the freeze has been lifted earlier today, now that Airflow 3.1 is released. Feel free to make modifications in the English translation :)
Shahar On Fri, Sep 12, 2025 at 10:18 AM Shahar Epstein <[email protected]> wrote: > Hey everyone, > > Apologies for the delayed update - the freeze is prolonged until the final > release (which should be during the next week, hopefully). > > > Shahar > > On Mon, Aug 18, 2025, 22:50 Shahar Epstein <[email protected]> wrote: > >> Hey everyone, >> >> I'm sending this message on behalf of the release managers. >> The release managers are planning to cut the Airflow 3.1 RC in the >> beginning of the next month, >> where the i18n feature is planned to be released for the first time >> (thanks for everyone involved!). >> >> After running the i18n completeness script, this is the current coverage >> of each merged locale (as of Aug. 18, 2025): >> Dutch - 100% >> Hebrew - 100% >> Arabic - 100% >> Korean - 100%* (after merging #54611) >> Taiwanese Mandarin - 99.5% >> German - 98.6% >> Polish - 98.6% >> Spanish - 87.6% >> French - 86.8% >> >> There are two open PRs for adding languages (Portuguese - #52341, Italian >> - #52342), the coverage of each is 90.1%. >> Generally we're in good shape, but we could definitely make it to 100% in >> all locales (+ merge the open PRs where both are completed)! >> >> *Timeline:* >> >> - *English locale freeze (Sep 1–9, 2025):* During this period, I'd >> like to ask comitters to avoid merging PRs that modify the default locale >> (English), to prevent overloading the translators. >> - *Translation deadline (Sep 9, 2025):* Code owners, translation >> owners, and engaged translators are asked to complete their assigned >> locales, run the i18n completeness script locally, and reply to this email >> once done. Any changes after this date might not be included in the >> release >> — missing terms will fall back to English. >> >> *Important Notes:* >> 1. In a separate thread, I plan to raise a lazy consensus that defines >> the min. required coverage as 90% for locale to be included in a release. >> 2. If you plan to add a new translation anytime soon - please ensure that >> its coverage is above the min. threshold by Sep 1., and 100% by Sep 9 :) >> >> >> Thanks for your cooperation! >> Shahar Epstein >> >
