tisonkun commented on issue #252:
URL: 
https://github.com/apache/datasketches-rust/issues/252#issuecomment-5487214179

   Release checklist for 0.5.0, following `RELEASE.md`:
   
   ### Release preparation
   
   - [x] Resolve the originally identified blocker in #250.
   - [x] Complete the release-facing API, correctness, documentation, test, and 
package audit.
   - [x] Open release-preparation PR #257.
   - [x] Set `datasketches` and the lockfile package version to `0.5.0`.
   - [x] Freeze the accumulated changelog entries under an undated `v0.5.0` 
section.
   - [x] Pass the local release checks: testdata preparation, lint, feature 
checks, tests, package-file verification, and publish dry-run.
   - [ ] Pass all required CI checks on #257 and obtain review approval.
   - [ ] Merge #257 into `main` and record the exact release commit.
   
   ### Release candidate 1
   
   - [ ] Confirm crates.io, GPG/`KEYS`, and ASF SVN prerequisites for the 
release manager.
   - [ ] Create and push the immutable annotated tag `0.5.0-rc.1` from the 
approved release commit.
   - [ ] Publish the convenience prerelease crate `[email protected]` to 
crates.io.
   - [ ] Build `apache-datasketches-rust-0.5.0-src.zip` directly from the RC 
tag.
   - [ ] Create and locally verify the detached signature and SHA-512 checksum.
   - [ ] Stage exactly the source archive, signature, and checksum under 
`dist/dev/datasketches/rust/0.5.0-rc.1`.
   - [ ] Download and verify the staged candidate, then rerun the complete 
release checks from the source archive.
   - [ ] Send `[VOTE] Release Apache DataSketches Rust 0.5.0 (RC1)` to 
`[email protected]`, with a deadline at least 72 hours later.
   - [ ] Receive at least three binding PMC `+1` votes and more binding `+1` 
than binding `-1` votes.
   - [ ] Send the `[RESULT][VOTE]` message with binding and non-binding totals.
   
   ### Publish the approved release
   
   - [ ] Move the exact approved artifacts from `dist/dev` to 
`dist/release/datasketches/rust/0.5.0` without rebuilding them.
   - [ ] Create and push the annotated final tag `0.5.0` from the approved RC 
commit.
   - [ ] Publish and verify `[email protected]` on crates.io.
   - [ ] Verify the source archive on `downloads.apache.org`.
   - [ ] Remove `0.4.0` from `dist/release` after confirming the new release; 
the old release remains in the Apache archive.
   - [ ] Regenerate and publish the website download table, then verify its 
artifact, signature, checksum, and `KEYS` links.
   - [ ] Wait at least one hour after the release appears on 
`downloads.apache.org`, then announce it to `[email protected]` and 
`[email protected]`.
   - [ ] Submit the post-release changelog-date PR and close this tracking 
issue.
   
   If RC1 is cancelled, remove its `dist/dev` candidate, fix the issue through 
a new PR, and restart with a new immutable `0.5.0-rc.N` tag.
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to