This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow-steward.git
The following commit(s) were added to refs/heads/main by this push:
new 57e75b4 chore(asf.yaml): route notifications to Airflow PMC lists;
retire dev-magpie@ sequester (#282)
57e75b4 is described below
commit 57e75b438b1603e9f3b62e2b008e0a7a64f712d9
Author: Jarek Potiuk <[email protected]>
AuthorDate: Mon May 25 18:33:54 2026 +0200
chore(asf.yaml): route notifications to Airflow PMC lists; retire
dev-magpie@ sequester (#282)
The framework's commit / PR / issue / discussion traffic now lands
on the Airflow PMC's own `commits@` and `jobs@` lists rather than
the dedicated `[email protected]` sub-list set up in
#271.
Rationale: traffic volume on the Airflow PMC's lists is already
strong and noisy enough that adding this repo's events does not
materially change the signal/noise profile. The cost of subscribers
having to follow a separate sub-list to see what was happening
here turned out to outweigh the value of keeping that traffic
sequestered. When the framework eventually moves to its own TLP it
will inherit its own `commits@` list and the schemes will be
re-pointed at that list in the same change.
Routing follows Airflow's `.asf.yaml` destinations:
- `jobs` -> `[email protected]` (CI run notifications)
- everything else -> `[email protected]`
The four `_status` / `_comment` schemes (`issues_status`,
`issues_comment`, `pullrequests_status`, `pullrequests_comment`)
are set explicitly to `commits@` here rather than left at the ASF
Infra dev@ default, so PR review comments, CI-status flips, and
label / milestone changes land on the same list as the lifecycle
events instead of polluting `[email protected]`. This is
where the routing differs from Airflow's own asf.yaml: Airflow
accepts those events on `dev@`; the framework keeps them on
`commits@` to consolidate.
`commits_by_path` remains the only intentionally-unset scheme (it
is an optional path-specific override, not a default-suppression
risk). If ASF Infra adds a new scheme, set it explicitly in the
same change to keep the `dev@` default suppressed.
No cross-references to `dev-magpie@` remain in the repo (grepped
across all markdown / yaml; only `.asf.yaml` referenced it).
Generated-by: Claude Code (Opus 4.7)
---
.asf.yaml | 71 +++++++++++++++++++++++++++++----------------------------------
1 file changed, 33 insertions(+), 38 deletions(-)
diff --git a/.asf.yaml b/.asf.yaml
index dea0628..a6bb856 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -179,45 +179,40 @@ github:
required_signatures: false
notifications:
- # The framework is hosted under the Airflow PMC umbrella for now,
- # but all notification streams from this repo are routed to the
- # dedicated `[email protected]` sub-list so that the
- # Airflow PMC's main `dev@`, `commits@`, and `jobs@` lists are not
- # polluted with framework traffic. The sub-list belongs to the
- # nascent Magpie effort (see `MISSION.md` /
- # `docs/board-resolution-draft.md`) and will move with the repo
- # when it relocates to its own TLP.
+ # The framework is hosted under the Airflow PMC umbrella, and its
+ # commit / PR / issue / discussion traffic lands on the PMC's own
+ # lists rather than the previously-used `dev-magpie@` sub-list.
+ # Traffic volume on the Airflow PMC's lists is already strong and
+ # noisy enough that adding this repo's events does not materially
+ # change the signal/noise profile — separating them onto a
+ # dedicated sub-list was not worth the cost of subscribers having
+ # to follow a second list to see what was happening here. When the
+ # framework eventually moves to its own TLP it will inherit its
+ # own `commits@` list and the schemes below will be re-pointed at
+ # that list in the same change.
#
- # IMPORTANT: do **not** route any notification stream to
- # `[email protected]`, `[email protected]`, or
- # `[email protected]`. Those are the Airflow PMC's main
- # lists; every PR, issue, push, comment, and status-check event
- # from this repo does not belong there.
+ # Routing follows Airflow's `.asf.yaml` destinations:
+ # - jobs → jobs@ (CI run notifications)
+ # - everything else → commits@
#
# ASF Infra defaults any *unset* notification field to
- # `dev@<project>.apache.org`, so **every documented scheme below
- # MUST stay explicitly populated** — dropping a line here silently
- # re-enables that dev@ default for that event type. Per the ASF
- # asf.yaml schema
+ # `dev@<project>.apache.org`. The four `_status` / `_comment`
+ # schemes (`issues_status`, `issues_comment`, `pullrequests_status`,
+ # `pullrequests_comment`) are set explicitly to `commits@` here —
+ # **not** left to that default — so PR review comments, CI-status
+ # flips, and label / milestone changes go to the same list as the
+ # lifecycle events rather than landing on `[email protected]`.
+ # Per the ASF asf.yaml schema
#
(https://github.com/apache/infrastructure-asfyaml/blob/main/asfyaml/feature/notifications.py
- # `VALID_NOTIFICATION_SCHEMES`), the schemes that apply to a public
- # GitHub repo are the eleven below (we set ten; `commits_by_path`
- # is an optional path-specific override and is left unset). If
- # Infra adds a new scheme, set it explicitly in the same change to
- # keep the dev@ default suppressed.
- #
- # All ten schemes go to a single list — `dev-magpie@` — by design:
- # the Magpie sub-list is the one place a subscriber needs to watch
- # to follow the framework end-to-end (CI, commits, issues, PRs,
- # discussions). When the repo gets its own TLP and the list shape
- # diversifies (a dedicated commits@ / jobs@ under the new PMC),
- # split the schemes across those lists then.
- jobs: [email protected]
- commits: [email protected]
- issues: [email protected]
- issues_status: [email protected]
- issues_comment: [email protected]
- pullrequests: [email protected]
- pullrequests_status: [email protected]
- pullrequests_comment: [email protected]
- discussions: [email protected]
+ # `VALID_NOTIFICATION_SCHEMES`), if Infra adds a new scheme, set
+ # it explicitly in the same change to keep the `dev@` default
+ # suppressed.
+ jobs: [email protected]
+ commits: [email protected]
+ issues: [email protected]
+ issues_status: [email protected]
+ issues_comment: [email protected]
+ pullrequests: [email protected]
+ pullrequests_status: [email protected]
+ pullrequests_comment: [email protected]
+ discussions: [email protected]
