[VOTE] Release Apache Iggy (incubating) v0.5.0

[spetz]

Hello, Apache Iggy (incubating) Community,

This is a call for a vote to release Apache Iggy (incubating) version 0.5.0

Along with the Iggy Server 0.5.0 we will release SDKs and tooling such as Web UI, Bench Dashboard, CLI, Bench CLI, Connectors Runtime and MCP server.

Git commit for the release:
7ebaf9b

The change lists about this release:

server-0.4.300...server-0.5.0-rc.1

Git tag for the release:

https://github.com/apache/iggy/releases/tag/server-0.5.0-rc.1

The release candidate:

https://dist.apache.org/repos/dist/dev/incubator/iggy/0.5.0/

The artifacts signed with PGP key 24A4364E, corresponding to [email protected], that can be found in keys file:
https://dist.apache.org/repos/dist/dev/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 until the necessary number of votes are reached.

Please vote accordingly:

• +1 approve
• +0 no opinion
• -1 disapprove with the reason

To learn more about Iggy, please see https://iggy.apache.org

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.

Verify source

To verify the source code, at first clone the repository and then simply 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:

405014586a1a4954fe5010fc5be5603585d230c9aa7cdc890991506954b52a5f8848510c1f760cbcd8350dd09b74de9f8331f6a22335350d97ff84ba41502e0f

Build and test

To build, you need to have Rust installed.

Then, simply type cargo build and next cargo test to ensure that everything does work as expected.

Thanks,
Piotr Gankiewicz

[T1B0]

let's go to release 🚀

• +1 approve (binding Apache PPMC)

checklist:

• 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.

[hubcio]

+1 (binding, apache PPMC)
checked everything from checklist, LGTM

[numinnex]

+1 (binding Apache PPMC)

• Download links are 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

[lukaszzborek]

+1
LGTM

[yonik]

Hmmm, I got a test failure on my first try:

test streaming::segment::should_delete_persisted_segments ... ok

failures:

---- streaming::segment::given_all_expired_messages_segment_should_be_expired stdout ----

thread 'streaming::segment::given_all_expired_messages_segment_should_be_expired' panicked at core/integration/tests/streaming/segment.rs:368:5:
assertion failed: !segment.is_expired(not_expired_ts).await
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    streaming::segment::given_all_expired_messages_segment_should_be_expired

test result: FAILED. 1141 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 26.89s

Logs for failed test 'streaming::segment::given_all_expired_messages_segment_should_be_expired':
2025-08-04 18:15:48.293558  INFO - Initializing MemoryPool with 32 buckets, each will have capacity: 8192.
2025-08-04 18:15:48.293706  WARN - Memory pool already initialized.
2025-08-04 18:15:48.294218  INFO - Saving segment with start offset: 0 for partition with ID: 3 for topic with ID: 2 and stream with ID: 1
2025-08-04 18:15:48.294381  INFO - Saved segment log file with start offset: 0 for partition with ID: 3 for topic with ID: 2 and stream with ID: 1
2025-08-04 18:15:48.484595  INFO - Closed segment with start offset: 0, end offset: 9, size: 600 B for partition with ID: 3.

error: test failed, to rerun pass `-p integration --test mod`

And then on rerun:

failures:
    server::general::matrix::transport_tcp_message_headers_scenario_expects

test result: FAILED. 1141 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 27.20s

Logs for failed test 'server::general::matrix::transport_tcp_message_headers_scenario_expects':
2025-08-04 18:21:31.840439  INFO - Iggy client is connecting to server: 127.0.0.1:45933...
2025-08-04 18:21:31.840691  INFO - Iggy client: 127.0.0.1:52620 has connected to server: 127.0.0.1:45933 at: 2025-08-04 22:21:31
2025-08-04 18:21:31.840764  INFO - Automatic sign-in is disabled.

error: test failed, to rerun pass `-p integration --test mod`

Something funky with my system? I'm on Ubuntu 25.04, with a fresh install of rust via rustup.

~/Downloads/tmp$ rustc --version
rustc 1.88.0 (6b00bc388 2025-06-23)
~/Downloads/tmp$ cargo --version
cargo 1.88.0 (873a06493 2025-05-10)

[jadireddi]

+1

[spetz]

@yonik do you get any errrors when you run these tests separately?

cargo test given_all_expired_messages_segment_should_be_expired

cargo test transport_tcp_message_headers_scenario_expects

If that works, could you either try rerunning it all with cargo test, or nextest?

cargo install cargo-nextest

cargo nextest run

[yonik]

It fails intermittently with both cargo test and nextest (often it is transport_quic_multiple_clients_scenario_expects that fails.) I can't get a test to fail running it by itself, so maybe interference among tests.

[spetz]

@yonik but if you run these as a single test only, does it succeed? Also, could you try running e.g. cargo test -- --test-threads 1 of course, you can provide any number from 1..N threads. With just a single one in place, it will take longer to run, but will not fail due to any concurrency or parallelism issues. I've had the following issue in the past in one of the projects, when using too many test containers at once, but it's hard to reproduce in Iggy, as it works locally on our machines, and also on GitHub CI.

[yonik]

but if you run these as a single test only, does it succeed?

Yes. That's what I meant by "I can't get a test to fail running it by itself"

[spetz]

Right, it was my misunderstanding :) Please give it a try with the limited thread number.

[yonik]

I've opened #2082 to avoid polluting this issue more since it seems to just be a test issue. Will let you know how single-threaded goes.

[krishvishal]

+1
LGTM

[haze518]

Hey, am I doing something wrong? My checksum doesn’t match on 7ebaf9b

➜  iggy git:(server-0.5.0-rc.1) ./scripts/prepare-release.sh  
Preparing release for version: 0.5.0
Release directory: iggy_release
SHA-512 checksum:
42d33ad3a220e670db946cc6e49a75f80044c3d4998af90ab65cf8a56d5a3eb12b1b36a991b782c0ab7581caff5fe232d3685f1b20b307f00a6d73d27759f3dd  iggy-0.5.0-incubating-src.tar.gz
✔ Archive created: iggy-0.5.0-incubating-src.tar.gz
✔ Checksum saved to: iggy-0.5.0-incubating-src.tar.gz.sha512

[spetz]

@haze518 I've noticed that the checksum may differ, depending on OS, the one I posted was from latest MacOS. The release script should produce the same checksum, as it does reset all the metadata for archive etc. but maybe there's something else missing. It's tar on linux, and gtar on mac, which could make a difference? Also, make sure to git checkout server-0.5.0-rc.1 and run the script on the clean repo.

[haze518]

yeah, it was an issue on my side. I re-ran the script and now everything is good

➜  iggy git:(server-0.5.0-rc.1) ./scripts/prepare-release.sh  
Preparing release for version: 0.5.0
Release directory: iggy_release
SHA-512 checksum:
405014586a1a4954fe5010fc5be5603585d230c9aa7cdc890991506954b52a5f8848510c1f760cbcd8350dd09b74de9f8331f6a22335350d97ff84ba41502e0f  iggy-0.5.0-incubating-src.tar.gz
✔ Archive created: iggy-0.5.0-incubating-src.tar.gz
✔ Checksum saved to: iggy-0.5.0-incubating-src.tar.gz.sha512

+1 LGTM!

[kparisa]

+1 (binding Apache PPMC)

• Download links are 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

Super excited about this release with a lot of goodies :)

[Xuanwo]

+1 binding

• 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.

[thepatrykk]

+1 (binding Apache PPMC)

• Download links are 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

[jaroslawroszyk]

[spetz]

Hey @jaroslawroszyk thanks for sending your vote, but please keep in mind that it's not a binding vote from your side, as currently, you're not part of PPMC