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

Jean-Baptiste Onofré <[email protected]>
Newsgroups gmane.comp.apache.incubator.general
Message-ID <CAB8EV3SeeK4dkWfiHm7-6fxGYXveEYJo7cxDhQk++_CBZsbqug@mail.gmail.com>
+1 (binding)

I checked:
- source distribution
-- incubating is in the name/version
-- signature and checksum are good
-- LICENSE and NOTICE are good
-- ASF header is present in expected file
-- No binary/compiled file found in the source distribution (nit: I see
iggy.pfx in core/certs, waiting worth to resolve differently, not a
blocker).

Regards
JB

On Tue, Apr 7, 2026 at 7:03 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 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
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.