I don’t think this should apply until 3.1.0 is out and internationalisation is released.
Basically it can be out of date as long as the translation gap is closed for 3.1.0. IMHO On Mon 4 Aug 2025 at 22:13, Shahar Epstein <sha...@apache.org> wrote: > Hey everyone, > > I'd like to point out that the Dutch locale has been out of sync for quite > a while - less than 14% coverage, which is fairly low. > There has been a PR for fixing it, yet it progresses quite slow: > https://github.com/apache/airflow/pull/51233 > > As we're getting closer to a 2nd consecutive release with low coverage, > according to section 6.4 in the i18n policy - it might be suggested for > deletion. I'd rather avoid making harsh steps, as efforts were invested > (which were and are highly appreciated!) - so I'd like to ask the current > owners, and any other Dutch speaker within the dev list, to help increase > the translation coverage (could be done in small PRs). However, I don't > think that we should handle the current situation for too long, as this is > what we deliver to the end-users. > > I'll be happy to hear the opinions of the community about what we should do > in this situation and similar situations in the future - do you think that > the current policy handles it well in its current form, should we make it > more strict/loose? > > > Shahar >
