shahar1 opened a new pull request, #73883: URL: https://github.com/apache/airflow/pull/73883
The providers `[RESULT][VOTE]` template did not cover two cases that come up in most waves. Some voters give `+1` for only some providers. Some providers are excluded after `-1` votes. The template also repeated "(binding)" after every name under a heading that already says the votes are binding. The 2026-09-22 wave had both cases. PoAn Yang voted `+1` for amazon, apache.beam and google only, and `-1` for edge3. edge3 and cncf.kubernetes were excluded after `-1` votes. This PR: - Updates the template and its instructions in `dev/README_RELEASE_PROVIDERS.md`. Binding `+1` voters are listed by name only. Non-binding `+1` voters are split into a whole-set list and a specific-providers list. Each excluded provider gets its binding and non-binding `-1` tally. - Adds `.apache-magpie-overrides/release-vote-tally.md`, so agents running the magpie `vote-tally` skill follow the same rules. It also adapts the skill to providers waves: a wave is identified by its preparation date, has no planning issue or RC labels, and scoped votes are not treated as ambiguous. A `+1` counts for specific providers only when its vote line names them. A plain `+1` from someone who adds that they only tested their own changes counts for the whole set. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 5.5) Generated-by: Claude Code (Opus 5.5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- 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]
