Anyone knows Hungarian or Finish or Estonian? That would be nice to have - we have I think many families of languages but we miss https://en.wikipedia.org/wiki/Uralic_languages :) Also I believe we even some committers in Japan, that would be really cool... and Portuguese... We have a lot of users in Brazil !
J. On Mon, Aug 18, 2025 at 10:33 PM Brent Bovenzi <br...@astronomer.io.invalid> wrote: > Thanks for taking this on Shahar. The deadlines and 90% coverage consensus > make sense to me! > > I also just reopened the PR for Hindi. Would be great if anyone can help > get that across the finish line too! > https://github.com/apache/airflow/pull/51281 > I'd love to launch 3.1.0 with 12 languages beyond English! > > On Mon, Aug 18, 2025 at 4:14 PM Jarek Potiuk <ja...@potiuk.com> wrote: > > > 1.4% PR for PL -> https://github.com/apache/airflow/pull/54633 > > > > On Mon, Aug 18, 2025 at 9:51 PM Shahar Epstein <sha...@apache.org> > 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 > > > > > >
