diff --git a/audit/releases/0.1.0.md b/audit/releases/0.1.0.md new file mode 100644 index 00000000..2b338f56 --- /dev/null +++ b/audit/releases/0.1.0.md @@ -0,0 +1,49 @@ + + +**Table of Contents** *generated with [DocToc](https://github.com/thlorenz/doctoc)* + +- [Release audit: Apache Magpie 0.1.0](#release-audit-apache-magpie-010) + - [Artefacts](#artefacts) + - [Notes](#notes) + + + + + +# Release audit: Apache Magpie 0.1.0 + +| Field | Value | +|---|---| +| Version | `0.1.0` | +| RC | `rc2` | +| Vote thread | https://lists.apache.org/thread/tm2vfng6q2kf5ovzqx837fqxlfrpg94t | +| Result thread | https://lists.apache.org/thread/1x6w97tcjjtf60yj7qlnbb2zk8cw6791 | +| Binding +1 | 4 | +| Binding -1 | 0 | +| Binding voters | `potiuk`, `kirs`, `zeroshade`, `rbowen` | +| Promote revision | `r86074` | +| Announcement | https://lists.apache.org/thread/vyo4cl2ssv1hxz6f0zz14y3kjko7j9po | + +## Artefacts + +| File | SHA-512 | Signature | +|---|---|---| +| `apache-magpie-0.1.0-source.zip` | `991218c7ecbe66a5ccf4b6e5b55cedee33382d8f38d1bd8683a45303771e8d43cd106acd371931801450ed77d993c9c778fd03f0c231eb892adb7f8b21af3568` | `apache-magpie-0.1.0-source.zip.asc` | + +## Notes + +- First Apache Magpie release. Released from `0.1.0-rc2` = commit `1890a13d`; + the final GPG-signed `0.1.0` tag is on the same commit. +- Non-binding +1: Milamber. The vote reached quorum on 2026-07-17 (the 72h + window is a floor, not a close). +- The rc2 `[VOTE]` was administered via the ATR platform but re-issued as a + traditional (non-ATR) `dev@` vote after a process objection; the traditional + thread (linked above) is authoritative for the tally. +- Promote commit `r86074` (potiuk, 2026-07-19 00:24 CEST): `svn mv` of + `dist/dev/magpie/0.1.0-rc2` → `dist/release/magpie/0.1.0`. +- No gaps or anomalies detected; no redactions (no security-tracker content in scope). + +--- +*Generated by `release-audit-report` (magpie-release-audit-report). +Source: planning issue https://github.com/apache/magpie/issues/776.* diff --git a/skills/release-audit-report/SKILL.md b/skills/release-audit-report/SKILL.md index e513c06e..5a974000 100644 --- a/skills/release-audit-report/SKILL.md +++ b/skills/release-audit-report/SKILL.md @@ -213,15 +213,30 @@ the configured archive backend, and `/release-management-config. | `product_name` | `release-management-config.md` (`product_name` key) | `` | | `planning_issue_url` | detected or supplied | — | | `rc_label` | planning issue body (e.g. "rc1") | `MISSING` | -| `vote_thread_url` | planning issue body (`[VOTE]` archive URL) | `MISSING` | -| `result_thread_url` | planning issue body (`[RESULT]` archive URL) | `MISSING` | +| `vote_thread_url` | planning issue body (`[VOTE]` archive URL); else resolve from the mail archive (see *Mail-archive resolution*) | `MISSING` | +| `result_thread_url` | planning issue body (`[RESULT]` archive URL); else resolve from the mail archive (see *Mail-archive resolution*) | `MISSING` | | `artefacts` | planning issue body (RC artefact list with sigs and checksums) | `MISSING` | -| `promote_revision` | planning issue body (SVN revision or backend equivalent of Step 10) | `MISSING` | -| `announce_archive_url` | planning issue body (`[ANNOUNCE]` archive URL) | `MISSING` | +| `promote_revision` | planning issue body; else, for `svnpubsub`, resolve via `svn info --show-item last-changed-revision ` (the Step 10 `svn mv` commit that created the promoted dir) | `MISSING` | +| `announce_archive_url` | planning issue body (`[ANNOUNCE]` archive URL); else resolve from the announce-list mail archive (see *Mail-archive resolution*) | `MISSING` | | `vote_binding_plus1` | vote tally from planning issue or `[RESULT]` thread | `MISSING` | | `vote_binding_minus1` | vote tally from planning issue or `[RESULT]` thread | `MISSING` | | `binding_voters` | roster handle list from `pmc-roster.md` crossed with `[RESULT]` | `MISSING` | +**Mail-archive resolution.** Before marking `vote_thread_url`, +`result_thread_url`, or `announce_archive_url` as `MISSING`, resolve each +one from the configured mail archive when it is not already on the planning +issue: search the archive named by `mail_archive` / +`mail_archive_url_template` (for ASF, PonyMail on `lists.apache.org`) for the +`[VOTE]` / `[RESULT] [VOTE]` / `[ANNOUNCE]` subject of ``, take the +matching thread's permalink (`https://lists.apache.org/thread/`), and +record it. The `[ANNOUNCE]` may index under `announce_list` **or** a cc'd +list (e.g. `dev@`), so search the cc'd list archive too before giving up. +Mark the field `MISSING` **only** when the archive returns no +match — e.g. the message was sent so recently it is not yet indexed — and +note in the record that it should be backfilled once indexed. This keeps the +audit record self-completing rather than depending on the URLs having been +pasted onto the planning issue. + **Privacy gate.** Before reading any field, check whether its source is a public surface. Fields whose source data exists only in the security tracker or in non-public mail are set to `REDACTED` with a reason note.