+1 Thanks Shahar for the clarifications and updates.
On 2025/09/13 15:09:20 Shahar Epstein wrote: > Hey everyone, > > Following the current experience with the i18n freeze time, I've raised a > PR where I introduced the following changes to the policy (see PR #55629 > <https://github.com/apache/airflow/pull/55629>): > - Clarified the responsibilities of code owners when they sponsor a single > translation owner without other proficient people involved (tl;dr - they > need to review the language aspects of the translation owner using a > trusted 3rd party of their choice, e.g., LLMs). > - Added a definition of completeness with a threshold (at least 90% > coverage), which takes into account potential gaps that could result either > from a freeze (or in the case of new translation - late merge). > - Added a requirement for approving freeze exemptions by at least 1 PMC > member in the Slack channel. > - Added guidelines for approving exemptions during freeze. > - Added an instruction for adding the "plurals" definition. > - Polished the definition of an inactive owner. > > Also, in the same PR, I introduced an update for related instructions for > the release managers to reflect the updated policy (+ suggesting the > delegation of these instructions to another committer, for reducing load). > > If no one objects within the next 3 days (Sep. 16th, 2025, 03:00 PM UTC), > I'll assume lazy consensus and merge the PR upon its approval. > Some of the suggested changes are already implemented in practice - I > wanted to make sure that they are formalized so we'll be aligned in the > next releases. > > > Shahar >
