Hey everyone, This is calling for a consensus on updating the i18n policy regarding the freeze instructions.
Link to the PR: https://github.com/apache/airflow/pull/59136 Link to discussion: https://lists.apache.org/thread/4spy9y5wrf7fx7dqg54v5g7pwjt0zx12 *Summary:* 1. Instead of requiring a freeze for *every *major or minor release, a freeze will be applied only when the median coverage across all languages is below the 90% threshold, or when deemed necessary by the release manager (e.g., when a critical UI feature introduces many new terms). The idea is to use the freeze when *many *changes need to be applied across *many *translations (well above 100 terms), and not when specific translation(s) are simply unmaintained for too long. 2. A simple completeness check *should *be performed in every minor and major release, after which a thread should be posted on the dev list asking code owners to ensure completion (90%+) by the RC release (a mail template is included in the PR). Non-completed translations after the due date should be tracked for the subsequent release. 3. A reminder should be sent in every patch release to keep up with latest i18n changes in the v3-X-test branch. The consensus will be reached on Thursday, December 11th, 2025, 20:30 UTC, unless there are any objections. Shahar
