You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@magpie.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2026/08/29 18:23:50 UTC

[PR] chore: remove the last apache-steward references [magpie]

potiuk opened a new pull request, #1123:
URL: https://github.com/apache/magpie/pull/1123

   ## Summary
   
   - The framework was renamed from `apache-steward` to Apache Magpie some time ago, but a handful
     of references outlived the rename. `git grep -i 'apache[-_ ]steward'` now returns nothing.
   - Drops **Step 0a — Migrate `apache-steward`-era naming** from `skills/setup/upgrade.md` and the
     matching *"Migrating a pre-Magpie (`apache-steward`) adopter"* section from
     `docs/setup/install-recipes.md`. The two contradicted each other: the upgrade skill claimed
     every run **performs this migration automatically**, while the install recipes said the
     framework **no longer ships an automated migration**. Neither statement survives, so the
     contradiction goes with them.
   - Two stale `setup-steward` skill references in `tools/github/source-control.md` → `magpie-setup`.
   - The framework's name in the AI-authorship-disclosure eval fixture → "Apache Magpie framework".
   
   ## Type of change
   
   - [x] Documentation (`docs/`, `README.md`, `CONTRIBUTING.md`)
   - [x] Skill change (`.claude/skills/<name>/`) — see note below on eval fixtures
   - [x] Tool / bridge contract (`tools/<system>/*.md`)
   
   ## Test plan
   
   - [x] `prek` passes on every changed file — doctoc (the removed TOC entry), markdownlint, lychee
         (no anchor left pointing at the deleted sections), `check-placeholders`,
         `skill-and-tool-validate`
   - [x] `uv run pytest` passes in `tools/skill-evals`
   - [x] Verified `.claude/skills/magpie-setup/upgrade.md` resolves through the symlink chain to the
         edited `skills/setup/upgrade.md` with zero `steward` hits
   - [x] No new eval fixture: this removes a migration path rather than changing skill behaviour,
         and the one fixture touched is a cosmetic framework-name string, not a decision input
   
   ## Notes for reviewers
   
   - **The judgement call worth checking is whether the migration path is still owed to anyone.**
     Removing Step 0a means an adopter still on the pre-rename layout gets no automated migration
     and no documented manual one. That is deliberate — the rename is long past and the two
     descriptions had already drifted apart — but if any adopter is known to still be on
     `.apache-steward*`, this should wait.
   - `apache/airflow-steward` is deliberately **kept** in the README acknowledgements. That is
     project provenance tied to the `NOTICE` attribution, not a stale label.
   - Five remaining hits for the word "steward" are the ordinary English verb/noun ("to steward its
     release flow", "act as a steward of the project") in `docs/vendor-neutrality.md`,
     `skills/contributor-nomination/assess.md`, and `tools/asf-svn/` — left alone.
   


-- 
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: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] chore: remove the last apache-steward references [magpie]

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #1123:
URL: https://github.com/apache/magpie/pull/1123


-- 
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: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org