My +1 binding

Thanks for your votes and I'll conclude the result now.

Best,
tison.


Pierre Lacave <[email protected]> 于2026年8月18日周二 21:30写道:

> +1 (binding)
>
>
> Artifact integrity
> - SHA-512 checksum: OK
> - GPG signature: OK signed by key 8B374472FAD328E17F479863B379691FC6E298DD
> (Zili Chen / [email protected]), present in the published KEYS file
> - Git tag 0.4.0-rc.1 resolves to 595516eca9ed320d14cb9815d8d87ebb79197edb:
> OK matches the announced commit
>
> Legal/package
> - LICENSE and NOTICE present at the source root: OK
> - No stray binary/artifacts in the source zip: OK
> - version = "0.4.0" in datasketches/Cargo.toml: OK
>
> Build/test checks
> - cargo package --list -p datasketches: clean file listing (no unexpected
> inclusions)
> - cargo publish --dry-run --locked -p datasketches: packages, verifies,
> and "uploads"
> - cargo x lint: OK
> - cargo x check (per-feature + all-features matrix): OK
> - cargo x test: OK, all suites pass, 0 failures across unit tests,
> doctests, and every integration test binary
>
> On Tue, Aug 18, 2026 at 10:31 AM Filippo Rossi <[email protected]> wrote:
>
>> +1 (binding)
>>
>> I verified Apache DataSketches Rust 0.4.0, release candidate 0.4.0-rc.1:
>>
>>    - The annotated Git tag resolves to commit
>>    595516eca9ed320d14cb9815d8d87ebb79197edb.
>>    - The crates.io release candidate is available.
>>    - The staged SHA-512 checksum matches
>>    
>> f833df73513f3cd760dc87492437c207e38dfbefc4938237cf70e75229f5181b0cdb85c97a075ae27d57d1ac2be52e8b7e9a89cf5614cf7a41d2fca659f4d961.
>>    - The source signature is valid and uses key
>>    8B374472FAD328E17F479863B379691FC6E298DD from the published KEYS file.
>>    - The staged source archive matches the proposed commit.
>>    - cargo package and cargo publish --dry-run passed.
>>    - cargo x prepare-testdata, cargo x lint, cargo x check, and cargo x
>>    test passed.
>>
>>
>> On Sat, Aug 15, 2026, at 11:39, Zejiong Dong wrote:
>>
>> +1 approve
>>
>> I verified the SHA-512 checksum and PGP signature (fingerprint
>> 8B374472FAD328E17F479863B379691FC6E298DD), confirmed the tag points to
>> 595516eca9ed320d14cb9815d8d87ebb79197edb, and ran all listed source checks
>> successfully, including cargo publish --dry-run, lint, feature-matrix
>> check,
>> and the full test suite.
>>
>> On 2026/08/13 13:35:42 tison wrote:
>> > Hi everyone,
>> >
>> > I propose releasing Apache DataSketches Rust version 0.4.0.
>> >
>> > The release candidate is based on commit:
>> > 595516eca9ed320d14cb9815d8d87ebb79197edb
>> >
>> > Source distribution:
>> > https://dist.apache.org/repos/dist/dev/datasketches/rust/0.4.0-rc.1/
>> >
>> > Git tag:
>> > https://github.com/apache/datasketches-rust/tree/0.4.0-rc.1
>> >
>> > Changelog:
>> >
>> https://github.com/apache/datasketches-rust/blob/0.4.0-rc.1/CHANGELOG.md
>> >
>> > crates.io release candidate:
>> > https://crates.io/crates/datasketches/0.4.0-rc.1
>> >
>> > Signing key fingerprint:
>> > 8B374472FAD328E17F479863B379691FC6E298DD
>> >
>> > KEYS:
>> > https://downloads.apache.org/datasketches/KEYS
>> >
>> > SHA-512:
>> >
>> f833df73513f3cd760dc87492437c207e38dfbefc4938237cf70e75229f5181b0cdb85c97a075ae27d57d1ac2be52e8b7e9a89cf5614cf7a41d2fca659f4d961
>> >  apache-datasketches-rust-0.4.0-src.zip
>> >
>> > Verification:
>> >   shasum -a 512 --check apache-datasketches-rust-0.4.0-src.zip.sha512
>> >   gpg --verify apache-datasketches-rust-0.4.0-src.zip.asc
>> > apache-datasketches-rust-0.4.0-src.zip
>> >
>> > Source checks:
>> >   export CARGO_TARGET_DIR="$(mktemp -d)"
>> >   cargo package --list -p datasketches
>> >   cargo publish --dry-run --locked -p datasketches
>> >   cargo x prepare-testdata
>> >   cargo x lint
>> >   cargo x check
>> >   cargo x test
>> >
>> > The vote will remain open until 2026-08-17 14:00 UTC,
>> > which is more than 72 hours from now.
>> >
>> > [ ] +1 approve
>> > [ ] +0 no opinion
>> > [ ] -1 disapprove, with a reason
>> >
>> > Best,
>> > tison.
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>>
>>

Reply via email to