Thanks Elad and Jens, Yes I did plan to send i18n translation catchup email tomorrow but thanks for sharing this. I will start a new thread with this as well.
yes I will move them to 3.3.0 > > @Rahul: There are also some fixes tagged to be 3.2.3 Milestone, will you > move them to 3.3.0? Regards, Rahul Vats On Sun, 7 Jun 2026 at 15:02, Jens Scheffler <[email protected]> wrote: > Thanks Rahul as well as Elad! > > To add also this is notw the time to catch-up with translations! A lot > seems to have fallen below the 90% threshold of coverage: > > Some translations are not complete! > > > Total Coverage per > Language > ┏━━━━━━━━━━┳━━━━━━━━━━┓ > ┃ Language ┃ Coverage ┃ > ┡━━━━━━━━━━╇━━━━━━━━━━┩ > │ ar │ 84.9% │ > │ ca │ 97.7% │ > │ de │ 97.7% │ > │ el │ 75.7% │ > │ es │ 77.5% │ > │ fr │ 97.8% │ > │ he │ 86.0% │ > │ hi │ 88.1% │ > │ hu │ 89.5% │ > │ it │ 77.7% │ > │ ja │ 80.7% │ > │ ko │ 97.8% │ > │ nl │ 92.4% │ > │ pl │ 97.7% │ > │ pt │ 89.3% │ > │ ru │ 88.2% │ > │ th │ 75.7% │ > │ tr │ 89.5% │ > │ zh-CN │ 89.4% │ > │ zh-TW │ 98.0% │ > │ │ │ > ├──────────┼──────────┤ > │ Median │ 89.4% │ > └──────────┴──────────┘ > > Jens > > Reminder, to fix-up use: breeze ui check-translation-completeness -l > <lang-code> --add-missing --remove-unused > > > @Rahul: There are also some fixes tagged to be 3.2.3 Milestone, will you > move them to 3.3.0? > > On 07.06.26 11:13, Elad Kalif wrote: > > Thanks Rahul > > > > We have 52 open PRs under the 3.3.0 milestone > > > https://github.com/apache/airflow/pulls?q=is%3Aopen+is%3Apr+milestone%3A%22Airflow+3.3.0%22 > > > > I'd like to ask everyone to spend some time on reviewing the list and > help > > merge what is ready. > > Community reviews are also very helpful and encouraged. > > > > > > On Sun, Jun 7, 2026 at 11:58 AM Rahul Vats<[email protected]> > wrote: > > > >> Dear Airflow Community, > >> > >> I will be cutting 3.3.0b1 in the week of 15th June 2026 as per 3.3.0 > >> timelines > >> < > >> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421958590#Airflow3.3-Airflow3.3Timelines > >> . > >> > >> > >> > >> I am planning to create the v3-3-test branch next week and keep it > mostly > >> in-sync with main until 15th June, which is the feature freeze date. > From > >> the freeze onward, any new features merged to main will *not* be > included > >> in 3.3. Work on existing new features is fine. > >> > >> > >> Let’s focus our efforts over the coming days on: > >> > >> - Completing ongoing 3.3 features and testing, including (but not > >> limited to) docs > >> coverage > >> - Prioritizing bugfixes > >> > >> This will help ensure we get a stable and solid release out the > >> door, tentatively planned for the end of the month. > >> > >> Finally, a call for action: I’ll need help with *release notes* & > *release > >> blog post* for new features in 3.3. > >> > >> - If you’ve worked on adding a new feature and would like it > >> highlighted, please either let me know or open a PR with a detailed > >> newsfragment for release notes > >> - For the blog post, please also send in your entries - screenshots > >> would be especially valuable for UI features. > >> > >> Thanks everyone, for your contributions! > >> > >> Regards, > >> Rahul Vats > >>
