andreahlert opened a new pull request, #67567:
URL: https://github.com/apache/airflow/pull/67567

   Add Portuguese (Brazil) - pt-BR - as a new supported UI locale.
   
   > Reopening of #62965 (closed; reopen disabled). Same branch, same scope.
   
   **Ownership (I am not an Apache Airflow committer):**
   
   - **Translation owner (proposed)**: @andreahlert.
   - **Code owner / translation sponsor (requested)**: I am asking a committer 
to act as code owner and, if needed, translation sponsor for this locale, so 
that the [approval process in section 
6.1](https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/ui/public/i18n/README.md#61-approval-of-ownership-candidates)
 can be carried out (including the dev list thread and PMC vote if the 
translation owner is a non-committer).
   
   Once a committer confirms they will act as code owner (and sponsor if 
applicable), the CODEOWNERS entry in this PR will be updated accordingly. After 
that, the usual approval and dev list steps from the i18n README can proceed.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [ ] Yes
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information.
   * This change adds a new supported locale; no AIP is required per the i18n 
policy.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to