P0-REL-E: Release Execution — Tag, PyPI Publish, Announce, Internal Docs Archive

[DingmaomaoBJTU]

Summary

Execute the final release: create git tag, publish to PyPI, announce on public channels, archive internal planning documents, and set up first-week monitoring.

Context

Release execution gate: June 1. Repo CANNOT go public until CELA + management approval confirmed (Reg-01 / L-07 from P0-REL-REG). From plans/release/0501_release_plan/release.md.

Tasks (E-01 ~ E-05)

• E-01: Create git release tag (v0.1.0) and GitHub Release with release notes — auto-generate from CHANGELOG; attach built wheel as asset
• E-02: Publish package to PyPI (pip install modelkit) — run full smoke test post-publish on clean environment
• E-03: Announce on relevant channels — blog post, LinkedIn, X, HN, Reddit r/MachineLearning; coordinate with marketing; prepare one-pager
• E-04: Archive or remove internal planning documents from public repo — move plans/ to a private wiki or redact before public push
• E-05: Post-release: monitor GitHub Issues for first-week bugs; respond within 48h — assign on-call rotation for first two weeks

Acceptance Criteria

• All blocking gates resolved (CELA + 1CS sign-offs, zero HIGH security findings, all tests pass)
• v0.1.0 tag created and GitHub Release published with release notes + wheel asset
• pip install modelkit succeeds on clean Windows + Linux environments
• wmk build google-bert/bert-base-uncased works on a freshly installed package
• Internal planning docs (plans/) removed or redacted from public repo
• Announcement drafted and published on at least 2 public channels
• On-call rotation assigned for first 2 weeks post-release

Technical Notes

• E-04 is BLOCKING: plans/ directory contains internal roadmaps with unreleased product decisions — must not be public
• E-02 smoke test: pip install modelkit && wmk build google-bert/bert-base-uncased --dry-run
• E-05: create a triage rotation doc; ensure all maintainers can close/label issues
• Announcement: coordinate timing with any partner announcements (AMD, Qualcomm, Intel)

Blocking Gates (all must be green before E-01)

1. CELA + management approval received (Reg-01, L-07)
2. SDL Security Review sign-off (1CS-02)
3. Privacy Review (PIA) sign-off (1CS-03)
4. MIT license applied (L-01) + LICENSE file (L-02)
5. PoliCheck clean (L-04) + secrets scan clean (S-02)
6. All tests pass on clean environment (C-05)
7. CLA bot configured (R-04)
8. Internal docs archived (E-04)

Related Files

• plans/release/0501_release_plan/release.md — E-01 ~ E-05 + Blocking Gates section