+1 (binding, IPMC)

I have checked:

- [x] Download Iggy is valid.
- [x] Checksums and PGP signatures are valid.
- [x] Source code distributions have correct names matching the current
release.
- [x] LICENSE and NOTICE files are correct.
- [x] No compiled archives bundled in source archive.

On Sun, 30 Nov 2025 at 05:00, Yonik Seeley <[email protected]> wrote:
>
> +1 to release (binding, IPMC)
>
> -Yonik
>
> On Thu, Nov 27, 2025 at 1:02 PM Piotr Gankiewicz <[email protected]>
> wrote:
>
> > Hello everyone,
> >
> > This is the third release of Apache Iggy (Incubating), a persistent message
> > streaming platform written in Rust, supporting QUIC, TCP, WebSocket and
> > HTTP transport protocols, capable of processing millions of messages per
> > second with ultra low latencies.
> > For more info, please visit https://iggy.apache.org
> >
> > This release has been voted on by the Apache Iggy Community.
> >
> > *Vote Thread:*
> > https://lists.apache.org/thread/1wn8fyoo5m0x3h546q5xt7v7ox4n3fbj
> >
> > The vote PASSED with:
> > - 12 +1 votes (6 binding PPMC, 6 non-binding)
> > - 0 -1 votes
> >
> > *Vote Summary Thread:*
> > https://lists.apache.org/thread/lq8025x8q3ss6rc3d7yo4nvoqlyf9k34
> >
> > *The release candidate:*
> > https://dist.apache.org/repos/dist/dev/incubator/iggy/0.6.0/
> >
> > *Git commit for the release:*
> >
> > https://github.com/apache/iggy/commit/4a9e215a4b6b1476daae8c4c3c34252b5162a240
> >
> > *Change log for this release:*
> > https://github.com/apache/iggy/compare/server-0.5.0...server-0.6.0-rc.1
> >
> > *Git tag for the release candidate:*
> > https://github.com/apache/iggy/releases/tag/server-0.6.0-rc.1
> >
> > The artifacts were signed with PGP key 24A4364E, corresponding to
> > [email protected], that can be found in keys file:
> > https://downloads.apache.org/incubator/iggy/KEYS
> >
> > The Git tags for release will be created after the voting passes at
> > https://github.com/apache/iggy/releases since our CI publishes the
> > artifacts to GitHub, when the new tag is pushed.
> >
> > The vote will be open for at least 72 hours. Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > *Checklist for reference:*
> > - [ ] Download Iggy is valid.
> > - [ ] Checksums and PGP signatures are valid.
> > - [ ] Source code distributions have correct names matching the current
> > release.
> > - [ ] LICENSE and NOTICE files are correct.
> > - [ ] All files have license headers if necessary.
> > - [ ] No compiled archives bundled in source archive.
> > - [ ] Can compile from source.
> >
> > *Verification Steps*
> > Requires [Rust](https://www.rust-lang.org/tools/install).
> >
> > Build `cargo build`
> >
> > Run Tests `cargo test`. If you'd experience any concurrency/parallel test
> > runner errors, try limiting the amount of threads e.g. `cargo test --
> > --test-threads 1`
> >
> > Iggy CLI can be installed with `cargo install iggy-cli` and then type
> > `iggy` for options
> >
> > More steps can be found here:
> > https://github.com/apache/iggy/?tab=readme-ov-file#quick-start
> >
> > To verify the source code, at first clone the repository, then `git
> > checkout server-0.6.0-rc.1`
> > and finally run the release script from the root directory:
> > `./scripts/prepare-release.sh`
> >
> > This will create the artifact under iggy_release directory, and should
> > produce the following SHA-512 checksum:
> >
> > MacOS:
> >
> >
> > 3807266d44b1b5ac552479b37cb9c2974b948fe78adfc02ec9b8822fabcdc37892a00b7a1e1fe5d891b2075165b1409981185cc9e900243cbd1c6aeec395801d
> >
> > Linux (Ubuntu)
> >
> >
> > ac8907bc14467162ee57f25061506376ee813c4398e26779d50a760aa82770efcf7fec91e0795f76c9b7c135ccf5a6ba27b813c093b9c9202f8830c8e7a9b12d
> >
> > Please keep in mind that checksum might differ on MacOS vs Linux
> > distribution either due to the internal implementation of tar vs gnu-tar or
> > how it's handling the archive metadata (part of the release script).
> >
> > Thanks,
> > Piotr Gankiewicz
> >



-- 
Best Regards,
- Hulk Lin

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

Reply via email to