magpie-release-vote-draft

<!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Placeholder convention (see ../../AGENTS.md#placeholder-convention-used-in-skill-files): <project-config> → adopter's project-config directory path <upstream> → adopter's public source repo (e.g. apache/airflow) <version> → release version string (e.g. 2.11.0) <rcN> → release candidate number (e.g. rc1) <version>-<rcN> → fully-qualified RC identifier (e.g. 2.11.0-rc1) <staging-url> → URL to the staged RC artefact directory <tag-url> → URL to the RC tag on the source repository <keys-url> → URL to the project KEYS file <changelog-url> → URL to the changelog for this release <vote-list> → configured vote mailing list (e.g. dev@airflow.apache.org) Substitute these with concrete values from the adopting project's <project-config>/release-management-config.md before running any command below. --> # release-vote-draft This skill drafts the `[VOTE]` email and planning-issue comment for an Apache-convention RC vote. It is Step 7 of the [release-management lifecycle](../../docs/release-management/process.md). The skill **never sends mail** and **never posts a comment** without explicit RM confirmation. Both outputs are paste-ready artefacts: the RM copies the email body into their mail client and sends it themselves; the planning-issue comment is propose...