[VOTE] Release Apache Iggy v0.9.0 rc1

[hubcio]

Hello, Apache Iggy Community,

This is a call for a vote to release Apache Iggy version 0.9.0.

This is the first release of Apache Iggy as a top-level project of the Apache Software Foundation, after the graduation from the Incubator on 2026-08-19.

Along with the Iggy Server 0.9.0 we will release the SDKs and tooling from the same repository: the Rust SDK 0.11.0, the CLI 0.14.0, the Connectors runtime 0.5.0, the MCP server 0.5.0, the Web UI 0.4.0, the Bench Dashboard 0.8.0, and the Python 0.9.0, Node.js 0.10.0, Java 0.9.0, C# 0.9.0 and Go v0.9.0 SDKs.

0.9.0 is the first server version with built-in replication based on Viewstamped Replication (VSR), a new binary wire protocol shared by all SDKs, and the promotion of the thread-per-core io_uring server. The discussion thread has a summary of the changes:
#3885

Git commit for the release:
71f2961

The change list for this release:
server-0.8.0...server-0.9.0-rc.1

Git tag for the release candidate:
https://github.com/apache/iggy/releases/tag/server-0.9.0-rc.1

The release candidate:
https://dist.apache.org/repos/dist/dev/iggy/0.9.0-rc1/

The artifacts are signed with PGP key 6CBBED6E59612FCE (fingerprint 8526 A28E 7BA8 DDEC 7B08 6ED4 6CBB ED6E 5961 2FCE), which belongs to hgruszecki@apache.org. The key is in the KEYS file:
https://downloads.apache.org/iggy/KEYS

The final release tags will be created after the vote passes.

The vote will be open for at least 72 hours. It passes with at least three +1 binding votes from PMC members and more +1 binding votes than -1 binding votes.

Everyone is welcome to vote. Please state whether your vote is binding and include your platform and verification results.

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 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 build and test the downloaded source archive.

Verify the download

curl -fLO https://downloads.apache.org/iggy/KEYS
curl -fLO https://dist.apache.org/repos/dist/dev/iggy/0.9.0-rc1/iggy-0.9.0-src.tar.gz
curl -fLO https://dist.apache.org/repos/dist/dev/iggy/0.9.0-rc1/iggy-0.9.0-src.tar.gz.asc
curl -fLO https://dist.apache.org/repos/dist/dev/iggy/0.9.0-rc1/iggy-0.9.0-src.tar.gz.sha512
gpg --import KEYS
gpg --verify iggy-0.9.0-src.tar.gz.asc iggy-0.9.0-src.tar.gz
sha512sum -c iggy-0.9.0-src.tar.gz.sha512

Build and test

To build, install Rust 1.98.0 with rustup. The archive has no rust-toolchain.toml, so select the toolchain explicitly.

On Debian/Ubuntu, install pkg-config, libhwloc-dev and libudev-dev alongside the native compiler and build tools.

tar -xzf iggy-0.9.0-src.tar.gz
cd iggy-0.9.0-src
rustup toolchain install 1.98.0
cargo +1.98.0 build --locked
cargo +1.98.0 test --locked

The integration tests need Docker. If tests fail because of resource contention on your machine, run them serially with cargo +1.98.0 test --locked -- --test-threads 1. Please report failures that this does not explain in this thread.

You might need to increase the maximum kernel locked memory limit and the open file descriptor limit, because the iggy tests use these resources intensively.

On Linux, the Apache Doris connector tests need a higher vm.max_map_count, because the Doris backend refuses to start below 2000000:

sudo sysctl -w vm.max_map_count=2000000

Optional: reproduce the source archive from Git

To reproduce the archive, clone the repository, check out commit 71f29618ba04917fded0ef5cd085c206fef0ee49 or tag server-0.9.0-rc.1, and run the release script from the root directory:

./scripts/prepare-release.sh

This creates the artifact under the iggy_release directory with the following SHA-512 checksum:

32e33c0a61df4c87f4f27864168fb5da6d1e22f81c4f1568375d3ec8414c6e9ec590133a5615260602c50334df6ecd2ccb4aed6cbf9c7d57cb96c62630a6e456

Different gzip implementations can produce different compressed bytes from the same tar archive. If your locally reproduced archive has a different checksum, compare its uncompressed tar using the command below. The downloaded release candidate must match its published checksum exactly.

gzip -dc iggy_release/iggy-0.9.0-src.tar.gz | sha512sum

Expected:

61fcda93121ee1537718a5e577b711e423775449fa42b32777f3c133d6e3a789ca76db8a723633ed8939d889efdc701ed289bb155252b83bcb6c670f9003be47

Thanks,
Hubert

[hubcio]

biggest release to the date!
checked everything in the original email checklist
+1 (binding)

[numinnex]

+1 (binding)

• 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 build and test the downloaded source archive.

[spetz]

+1 (binding)

• 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 build and test the downloaded source archive.

[Xuanwo]

+1 (binding)

Verified on Linux x86_64 with Rust 1.98.0:

• Checksums, signatures, licensing and source packaging checked.
• The source archive matches the release tag.
• The full default build and 2,014 unit tests passed.
• Server startup, HTTP ping, TCP connectivity and shutdown passed
  using a local .env file.

One non-blocking follow-up: setting IGGY_ENV_PATH triggers a
debug assertion during startup because the configuration provider
treats it as an unknown variable. Using a local .env file works.
It would be good to fix this in the next release.

Thanks,
Xuanwo

[hubcio]

thank you Xuanwo, yeah that's a bug, IGGY_ENV_PATH wasn't on the ignore list for that debug assert (same for a few other vars).
i think we broke it during migration of server-ng to server (legacy server removal).
release builds only print a warning, so nothing breaks there. i have a fix already: #4200

[krishvishal]

+1 (non-binding)

• 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 build and test the downloaded source archive.

[mmodzelewski]

+1 (non-binding)

it's great to see this being released

[landingpro]

+1 (non-bindind)

congratz

[lukaszzborek]

+1 (non-binding) 🚀

[kparisa]

+1 (binding)

• 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 build and test the downloaded source archive.

[kriti-sc]

+1 (non-bindind)

[slbotbm]

+1

[ryankert01]

+1 (non-binding)

All tested! Thanks for the rc effort!

[BartoszCiesla]

+1