Skip to content

Tracking issue to release 0.5.0 #252

Closed

Description

@tisonkun

This is the tracking issue for releasing 0.5.0.

cc @pmcgleenon @ariesdevil @notfilippo @PsiACE

I'm going to run the release process once #250 gets handled.

Activity

  1. PsiACE commented on Aug 31, 2026

    @PsiACE
    Member

    go ahead

  2. tisonkun commented on Sep 1, 2026

    @tisonkun
    MemberAuthor

    Release checklist for 0.5.0, following RELEASE.md:

    Release preparation

    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.
    • Publish and verify datasketches@0.5.0-rc.1 on crates.io.
    • Build apache-datasketches-rust-0.5.0-src.zip directly from the RC tag.
    • Sign the archive with fingerprint 8B374472FAD328E17F479863B379691FC6E298DD and create its SHA-512 checksum.
    • Verify the local archive, signature, checksum, legal files, and exact three-file artifact set.
    • Stage the candidate under dist/dev/datasketches/rust/0.5.0-rc.1 in SVN revision 87102.
    • Re-download the staged candidate into a fresh directory and rerun signature, checksum, package, lint, feature, test, and doctest verification.
    • Send [VOTE] Release Apache DataSketches Rust 0.5.0 (RC1) to dev@datasketches.apache.org: vote thread. Voting closes on 2026-09-04 06:00 UTC.
    • 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 and add its thread URL here: https://lists.apache.org/thread/11x6cyxfm1x0b970p5lo05zhgylhwl4r

    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 datasketches@0.5.0 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 dev@datasketches.apache.org and announce@apache.org and record the thread URLs here.
    • Submit the post-release changelog-date PR and close this tracking issue.

    Nonblocking process follow-up: #259 clarifies the public communication checkpoints and has passed CI. It does not change or invalidate RC1.

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions