You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Shahar Epstein <sh...@apache.org> on 2025/08/18 19:50:35 UTC
[REMINDER] Complete i18n locales for Airflow 3.1 RC by Sep. 9, 2025
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
Re: [REMINDER] Complete i18n locales for Airflow 3.1 RC by Sep. 9, 2025
Posted by Kaxil Naik <ka...@gmail.com>.
Thanks for helping to co-ordinate this Shahar, appreciate it.
On Mon, 18 Aug 2025 at 20:51, Shahar Epstein <sh...@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
>
Re: [REMINDER] Complete i18n locales for Airflow 3.1 RC by Sep. 9, 2025
Posted by Kaxil Naik <ka...@gmail.com>.
Thanks Shahar
On Fri, 26 Sept 2025 at 22:35, Shahar Epstein <sh...@apache.org> wrote:
> 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 <sh...@gmail.com>
> 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 <sh...@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
> >>
> >
>
Re: [REMINDER] Complete i18n locales for Airflow 3.1 RC by Sep. 9, 2025
Posted by Shahar Epstein <sh...@apache.org>.
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 <sh...@gmail.com> 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 <sh...@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
>>
>
Re: [REMINDER] Complete i18n locales for Airflow 3.1 RC by Sep. 9, 2025
Posted by Shahar Epstein <sh...@gmail.com>.
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 <sh...@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
>
Re: [REMINDER] Complete i18n locales for Airflow 3.1 RC by Sep. 9, 2025
Posted by Rahul Vats <ra...@gmail.com>.
Thanks, Shahar, for setting the threshold and coordinating this effort;
it’s really helpful from a testing perspective as well, since it gives code
owners clear deadlines to validate and perform testing before the release.
I’ll be working on the Hindi translations and will ensure they are in line
before the release.
Thanks again for driving this!
Regards,
Rahul
On Wed, 20 Aug 2025 at 21:09, Buğra Öztürk <oz...@gmail.com> wrote:
> We also have a Turkish one if someone willing to help me to review and be a
> Codeowner of translation. Please let me know and put any comment on the PR
> :) I can fill any gap if we have someone additionally
>
> https://github.com/apache/airflow/pull/51266
>
> Bugra Ozturk
>
> On Wed, 20 Aug 2025, 17:33 Jarek Potiuk, <ja...@potiuk.com> wrote:
>
> > Speaking of which: https://github.com/apache/airflow/pull/54716 - we
> have
> > now draft Hungarian translation :) ....
> >
> > Any more Hungarian-speaking people who could review it for a second pair
> > of eyes?
> >
> > On Wed, Aug 20, 2025 at 7:56 AM Amogh Desai <am...@apache.org>
> wrote:
> >
> > > Thanks for following this one closely, Shahar!
> > >
> > > Excited to see 10+ languages beyond English this time in 3.1!
> > >
> > > Thanks & Regards,
> > > Amogh Desai
> > >
> > >
> > > On Tue, Aug 19, 2025 at 2:27 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> > >
> > > > 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
> > > <brent@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 <
> shahar@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
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [REMINDER] Complete i18n locales for Airflow 3.1 RC by Sep. 9, 2025
Posted by Buğra Öztürk <oz...@gmail.com>.
We also have a Turkish one if someone willing to help me to review and be a
Codeowner of translation. Please let me know and put any comment on the PR
:) I can fill any gap if we have someone additionally
https://github.com/apache/airflow/pull/51266
Bugra Ozturk
On Wed, 20 Aug 2025, 17:33 Jarek Potiuk, <ja...@potiuk.com> wrote:
> Speaking of which: https://github.com/apache/airflow/pull/54716 - we have
> now draft Hungarian translation :) ....
>
> Any more Hungarian-speaking people who could review it for a second pair
> of eyes?
>
> On Wed, Aug 20, 2025 at 7:56 AM Amogh Desai <am...@apache.org> wrote:
>
> > Thanks for following this one closely, Shahar!
> >
> > Excited to see 10+ languages beyond English this time in 3.1!
> >
> > Thanks & Regards,
> > Amogh Desai
> >
> >
> > On Tue, Aug 19, 2025 at 2:27 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> >
> > > 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
> > <brent@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 <sh...@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
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [REMINDER] Complete i18n locales for Airflow 3.1 RC by Sep. 9, 2025
Posted by Jarek Potiuk <ja...@potiuk.com>.
Speaking of which: https://github.com/apache/airflow/pull/54716 - we have
now draft Hungarian translation :) ....
Any more Hungarian-speaking people who could review it for a second pair
of eyes?
On Wed, Aug 20, 2025 at 7:56 AM Amogh Desai <am...@apache.org> wrote:
> Thanks for following this one closely, Shahar!
>
> Excited to see 10+ languages beyond English this time in 3.1!
>
> Thanks & Regards,
> Amogh Desai
>
>
> On Tue, Aug 19, 2025 at 2:27 AM Jarek Potiuk <ja...@potiuk.com> wrote:
>
> > 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
> <brent@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 <sh...@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
> > > > >
> > > >
> > >
> >
>
Re: [REMINDER] Complete i18n locales for Airflow 3.1 RC by Sep. 9, 2025
Posted by Amogh Desai <am...@apache.org>.
Thanks for following this one closely, Shahar!
Excited to see 10+ languages beyond English this time in 3.1!
Thanks & Regards,
Amogh Desai
On Tue, Aug 19, 2025 at 2:27 AM Jarek Potiuk <ja...@potiuk.com> wrote:
> 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 <brent@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 <sh...@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
> > > >
> > >
> >
>
Re: [REMINDER] Complete i18n locales for Airflow 3.1 RC by Sep. 9, 2025
Posted by Jarek Potiuk <ja...@potiuk.com>.
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 <sh...@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
> > >
> >
>
Re: [REMINDER] Complete i18n locales for Airflow 3.1 RC by Sep. 9, 2025
Posted by Brent Bovenzi <br...@astronomer.io.INVALID>.
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 <sh...@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
> >
>
Re: [REMINDER] Complete i18n locales for Airflow 3.1 RC by Sep. 9, 2025
Posted by Jarek Potiuk <ja...@potiuk.com>.
1.4% PR for PL -> https://github.com/apache/airflow/pull/54633
On Mon, Aug 18, 2025 at 9:51 PM Shahar Epstein <sh...@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
>