Tracking Issue to Release 0.7.2

[tisonkun]

cc @apache/asyncband-committers

Release manager: @tisonkun

Target version: 0.7.2

Previous crates.io release: 0.7.1 (non-ASF release)

Current phase: Release preparation

Runbook: RELEASE.md

Previous release attempt: #227

The goal is to produce the first ASF-approved Apache Asyncband (Incubating) release after the unsuccessful 0.7.0 vote. The crates.io versions 0.7.0 and 0.7.1 were non-ASF releases; 0.7.0 has been yanked.

Release preparation

• Set the crate and lockfile version to 0.7.2 and prepare an undated v0.7.2 changelog section in #280.
• Preserve third-party license and copyright treatment in #279 and #281.
• Limit LICENSE to incorporated third-party works and record exact provenance in #283.
• Merge #284, which keeps RC tags off crates.io, removes the synthetic RC crate version, and records the 0.7.0 and 0.7.1 release dates.
• Decide whether to merge documentation-only #282 before the release freeze; otherwise defer it explicitly.
• Freeze the 0.7.2 scope and defer functional changes in #265, #253, #250, #247, #232, and #229.
• Remove the rejected 0.7.0-rc.1 candidate from dist/dev.
• Confirm the Unreleased section is empty and the v0.7.2 section contains the final user-visible changes.
• Reverify LICENSE, NOTICE, DISCLAIMER, source headers, bundled dependencies, and the contents of the Cargo package.
• Run cargo x lint, cargo x check, cargo x test --no-capture, the MSRV test, cargo x semver --release-version 0.7.2, and cargo publish --package asyncband --locked --dry-run on the final release commit.
• Record the merged release-preparation commit as RELEASE_COMMIT; every candidate artifact and tag must use this exact commit.

Release candidate

• Create and push signed tag v0.7.2-rc.1 from RELEASE_COMMIT.
• Confirm the Release workflow validates the RC tag, checks the unchanged 0.7.2 Cargo package with cargo publish --dry-run, and skips the crates.io publish job.
• Build apache-asyncband-0.7.2-incubating-src.tar.gz from the signed RC tag in a clean checkout.
• Create and verify its detached ASCII-armored signature and SHA-512 checksum.
• Verify the archive contents, legal files, unexpected binaries, tests, and Cargo package dry-run.
• Stage and reverify the candidate under dist/dev/incubator/asyncband/0.7.2-rc.1/.

PPMC vote

• Start [VOTE] Release Apache Asyncband (Incubating) 0.7.2 RC1 on dev@asyncband.apache.org and keep it open for at least 72 hours.
• Record the vote thread: pending.
• Obtain at least three PPMC +1 votes and a successful majority.
• Publish and record the PPMC result thread: pending.

IPMC vote

• Start the Incubator vote on general@incubator.apache.org with the PPMC result and archive link, and keep it open for at least 72 hours.
• Record the vote thread: pending.
• Obtain at least three binding IPMC +1 votes and a successful majority.
• Publish and record the IPMC result thread: pending.

Publish

• Promote the exact approved candidate from dist/dev to dist/release/incubator/asyncband/0.7.2/ without rebuilding it.
• Create and push signed tag v0.7.2 at the exact approved RELEASE_COMMIT.
• Approve the protected GitHub deployment and verify crates.io Trusted Publishing succeeds.
• Verify the release on downloads.apache.org, crates.io, docs.rs, and the ASF archive.
• Add the actual 0.7.2 publication date to the changelog heading in a post-release pull request.
• After the first successful OIDC publication, enable Require trusted publishing for all new versions in the crate settings.
• Announce Apache Asyncband (Incubating) 0.7.2 on the project mailing list and other appropriate channels.
• Close this tracking issue after the announcement and post-release checks are complete.