+1 (binding)

I would suggest clarifying the source distribution NOTICE file for the next
release.

I checked:
- source distribution
-- incubating is in the name/version
-- signature and checksum are good
-- DISCLAIMER is present
-- LICENSE and NOTICE are good. nit: the copyright year is still 2025 in
the NOTICE. Also, I think the mention of the DEPENDENCIES file is not
required in the NOTICE, as this NOTICE is for source distribution (so code
you have copied from another project). I would suggest clarifying this for
the next release (DEPENDENCIES mention is for a binary distribution NOTICE
in your case I guess).
-- Several files don't have ASF header (md files, properties files, go.mod
files, ...). It's not a blocker as it's not "pure" code source files, I
just wanted to inform :)
-- No binary/compiled file found in the source distribution.

Regards
JB

On Fri, Feb 20, 2026 at 10:24 PM Grzegorz Koszyk <[email protected]> wrote:

> Hello everyone,
>
> This is the fourth 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. It's the
> continuation of rc1 voting, where we addressed all the required
> improvements, and published the rc1 source release artifact.
>
> *Vote Thread:*
> https://lists.apache.org/thread/go9bmxb0rmc0qo4p6542g24lgz9h9fdh
>
> The vote PASSED with:
> - 9 +1 votes (5 binding, 4 non-binding)
> - 0 -1 votes
>
> *Vote Summary Thread:*
> https://lists.apache.org/thread/yfqk9mlkvz5qkzmmwgxjqk5zrd047w86
>
> *The release candidate:*
> https://dist.apache.org/repos/dist/dev/incubator/iggy/0.7.0-rc1/
>
> *Git commit for the release:*
>
> https://github.com/apache/iggy/commit/27281009373af7e68679145b39de19a1ace17dfd
>
> *Change log for this release:*
> https://github.com/apache/iggy/compare/server-0.6.0...server-0.7.0-rc1
>
> *Git tag for the release candidate:*
> https://github.com/apache/iggy/releases/tag/server-0.7.0-rc1
>
> The artifacts were signed with PGP key F7374995B0D75D9B, 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 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. 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'd experience any concurrency/parallel test
> runner errors, try limiting the amount of threads e.g. `cargo test --
> --test-threads 1`
>
> Iggy CLI can be installed with `cargo install iggy-cli` and then type
> `iggy` for options
>
> More steps can be found here:
> https://github.com/apache/iggy/?tab=readme-ov-file#quick-start
>
> To verify the source code, at first clone the repository, then `git
> checkout server-0.7.0-rc1`
> and finally 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:
>
> Linux (Ubuntu)
>
> 5a2b204220d12d580d30bde9a5efb8a268a8309b789beb046944a1eb9509b06cd29edcc7d5aa8e9b17cc338d37198f0d28aebd7e67f479881bc1a2c4114a6daa
>
> MacOS
>
> f1752f8cb4fa3a61c19ee05d87fd83cb55ce4e105d380e78edeecfb68f43e8cc92e06fe679958cbaf4d66f0a9c47e7e68dfe0ac7944305980133aff13dddbe8e
>
> Please keep in mind that checksum might differ on MacOS vs Linux
> distribution either due to the internal implementation of tar vs gnu-tar or
> how it's handling the archive metadata (part of the release script).
>
> Thanks,
> Grzegorz
>

Reply via email to