Re: [VOTE] Release Apache Iggy (Incubating) v0.8.0 rc1

Hi everyone,

Heads-up for this vote thread: we have decided to cancel the v0.8.0
release and re-cut as rc2.

Although the vote passed, we discovered post-vote that one of our
internal crates (`iobuf`) conflicts with an unrelated crate of the
same name already on crates.io (v5.8.1). This prevents us from
publishing `iggy_common` and `iggy_binary_protocol` without
embedding a dependency that would resolve to the wrong crate on
downstream users' machines.

The source tarball and the vote itself were valid; the issue is
a downstream Rust packaging problem that requires a code change.

The notice with details was also sent to this list here:
https://lists.apache.org/thread/kxny5bttbs38ncn2ntwjrbz311v51h90

Apologies to everyone who verified rc1 for the extra round of
verification work we're about to ask you for.

Thanks,
Hubert

On 2026/04/07 13:58:44 Hubert Gruszecki wrote:
> Hello everyone,
> 
> This is the fifth 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/0lwrn9b7b073cb1kl9xzxmopofzw1ndf
> 
> The vote PASSED with:
> - 12 +1 votes (5 binding, 7 non-binding)
> - 0 -1 votes
> 
> Vote Summary Thread:
> https://lists.apache.org/thread/7h97c0vsdjhp407op0op01zfrvj3skt2
> 
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/iggy/0.8.0-rc1/
> 
> Git commit for the release:
> https://github.com/apache/iggy/commit/7fca0f2d3a3c4a0f53b63e60af176c574683a3d2
> 
> Change log for this release:
> https://github.com/apache/iggy/compare/server-0.7.0...server-0.8.0-rc.1
> 
> Git tag for the release candidate:
> https://github.com/apache/iggy/releases/tag/server-0.8.0-rc.1
> 
> The artifacts were signed with PGP key 6CBBED6E59612FCE, 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.
> 
> 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 experience concurrency/parallel test runner errors, try limiting
> threads: cargo test -- --test-threads 1
> 
> To verify the source code, clone the repository, checkout to commit
> 7fca0f2d3a3c4a0f53b63e60af176c574683a3d2 or tag server-0.8.0-rc.1
> and 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:
> 
> b42fb9d1eb3c8b4d7a9d5372de0921140886006fb87eb7fe6735ac13ad2cfaf992bd34487e9b7f661a8cada40d4dd1d9c02813d58810079b4bc416fce60207c3
> 
> Please keep in mind that checksum might differ on MacOS vs Linux
> distribution due to the internal implementation of tar vs gnu-tar or
> how it's handling the archive metadata (part of the release script).
> 
> You might need to increase the maximum kernel locked memory limit and open
> file descriptors limit - iggy tests are quite intensive on these resources.
> 
> Thanks,
> Hubert
>