Re: [VOTE] Release Apache Iggy, Incubating, v0.8.0 rc2

+1 (binding)

Best regards
Alin J

On Tue, Apr 21, 2026 at 4:02 PM Jean-Baptiste Onofré <[email protected]>
wrote:

> +1 (binding)
>
> I checked:
> - source distribution
> -- incubating is in the name/version
> -- signature and checksum are good
> -- DISCLAIMER is present
> -- LICENSE and NOTICE are correct
> -- ASF header present in all expected files
> -- No binary/compiled file
>
> Regards
> JB
>
> On Sat, Apr 18, 2026 at 9:12 AM Hubert Gruszecki <[email protected]>
> 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 is a re-cut of v0.8.0 as rc2. The original v0.8.0 rc1 passed both
> > the Iggy community and IPMC votes, but during publishing we discovered
> > that one of our internal crates (`iobuf`) conflicts with an unrelated
> > crate of the same name already on crates.io (v5.8.1). That conflict
> > prevents us from publishing `iggy_common` and `iggy_binary_protocol`
> > to crates.io without pulling in the wrong dependency on downstream
> > users' machines. rc2 contains the fix for this issue; the rest of the
> > release is unchanged.
> >
> > Cancellation notice for v0.8.0 rc1:
> > https://lists.apache.org/thread/kxny5bttbs38ncn2ntwjrbz311v51h90
> >
> > This release has been voted on by the Apache Iggy Community.
> >
> > Vote Thread:
> > https://lists.apache.org/thread/0s1lzpxmzkr3gyw7cqqkc8gkblzj5vp2
> >
> > The vote PASSED with:
> > - 12 +1 votes (4 binding, 8 non-binding)
> > - 0 -1 votes
> >
> > Vote Summary Thread:
> > https://lists.apache.org/thread/qn1vyv8yclo4wdncso4w4pyflo6mgrtk
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/iggy/0.8.0-rc2/
> >
> > Git commit for the release:
> >
> >
> https://github.com/apache/iggy/commit/f5350d999d883fd3ca9dd33b3dc2754ddb0df049
> >
> > Change log for this release:
> > https://github.com/apache/iggy/compare/server-0.7.0...server-0.8.0-rc.2
> >
> > Git tag for the release candidate:
> > https://github.com/apache/iggy/releases/tag/server-0.8.0-rc.2
> >
> > 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
> > f5350d999d883fd3ca9dd33b3dc2754ddb0df049 or tag server-0.8.0-rc.2
> > 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:
> >
> >
> >
> 006a62c0bf988b20044743bb09ac780db42e3b63868705c521eb425686bad4208704d2152788f1584dfc06af8652c1e7b86dda474b05c79d926a71415f3e9b5d
> >
> > 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
> >
>