You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Piotr Gankiewicz <pi...@gmail.com> on 2025/11/27 18:02:08 UTC

[VOTE] Release Apache Iggy (Incubating) v0.6.0

Hello everyone,

This is the third 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/1wn8fyoo5m0x3h546q5xt7v7ox4n3fbj

The vote PASSED with:
- 12 +1 votes (6 binding PPMC, 6 non-binding)
- 0 -1 votes

*Vote Summary Thread:*
https://lists.apache.org/thread/lq8025x8q3ss6rc3d7yo4nvoqlyf9k34

*The release candidate:*
https://dist.apache.org/repos/dist/dev/incubator/iggy/0.6.0/

*Git commit for the release:*
https://github.com/apache/iggy/commit/4a9e215a4b6b1476daae8c4c3c34252b5162a240

*Change log for this release:*
https://github.com/apache/iggy/compare/server-0.5.0...server-0.6.0-rc.1

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

The artifacts were signed with PGP key 24A4364E, corresponding to
piotr@apache.org, 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.6.0-rc.1`
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:

MacOS:

3807266d44b1b5ac552479b37cb9c2974b948fe78adfc02ec9b8822fabcdc37892a00b7a1e1fe5d891b2075165b1409981185cc9e900243cbd1c6aeec395801d

Linux (Ubuntu)

ac8907bc14467162ee57f25061506376ee813c4398e26779d50a760aa82770efcf7fec91e0795f76c9b7c135ccf5a6ba27b813c093b9c9202f8830c8e7a9b12d

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,
Piotr Gankiewicz

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

Posted by Piotr Gankiewicz <pi...@apache.org>.
> To clarify:
> 1. If you plan to distribute only the source distribution, I'm +1 with the
> release
> 2. I was confused by the discussion because it mentioned binary
> distribution, but it doesn't appear to be present on dist.apache.org (maybe
> removed)
> 
> So, if you target only source distribution for this release, you have my +1
> 
> Regards
> JB
> 

Thank you, so we will prepare the improved rc2 source release and initiate the new voting.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi

To clarify:
1. If you plan to distribute only the source distribution, I'm +1 with the
release
2. I was confused by the discussion because it mentioned binary
distribution, but it doesn't appear to be present on dist.apache.org (maybe
removed)

So, if you target only source distribution for this release, you have my +1

Regards
JB

On Mon, Dec 1, 2025 at 5:15 PM Piotr Gankiewicz <pi...@apache.org> wrote:

> > Reverting my vote to -1 (binding) for the binary distribution for the
> > reasons mentioned earlier in the thread (source distribution is OK).
>
> Could you please elaborate on the binary distribution part (I wrote it a
> few comments back), as we only publish the source distribution? All the
> mentioned issues with some jar binary in the repository or missing headers
> etc. were resolved already, but before I will create an rc2 artifact, I
> just wanted to make sure that it's all ok.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

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

Posted by Piotr Gankiewicz <pi...@apache.org>.
We've opened a new voting thread for rc2 (looks like it got merged with the previous one due to the same title).

https://lists.apache.org/thread/fvjktho1b647yfzkmm5zwg52kh3cttxv

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by Piotr Gankiewicz <pi...@apache.org>.
> gradlew is useful but gradle installed on your build machine works just as well
> I wouldn't worry too much about not providing gradlew in source distributions.
> The Kafka/Iceberg gradlew file is fine and it's ok to include but
> Windows users can just install Gradle on their own machines.

Yes, we already got rid of Gradle, will be preparing the rc2 artifact later on today.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by PJ Fanning <fa...@gmail.com>.
gradlew is useful but gradle installed on your build machine works just as well
I wouldn't worry too much about not providing gradlew in source distributions.
The Kafka/Iceberg gradlew file is fine and it's ok to include but
Windows users can just install Gradle on their own machines.

On Tue, 2 Dec 2025 at 01:47, tison <wa...@gmail.com> wrote:
>
> Here is a solution to avoid bundling gradle.jar [1][2] in a source
> distribution: like mvnw, download the binary if it is missing.
>
> [1] https://github.com/apache/iceberg/blob/b35c7ec1b03e3897da68960cd556d635b2f5ae54/gradlew#L89-L91
> [2] https://github.com/apache/kafka/blob/a7246ff13853d51c0005effbe4d277fc8c50e511/gradlew#L203-L234
>
> They don't provide a version of gradlew.bat; instead, they delete it.
> I hope Windows users will be fine since there is WSL now.
>
> Best,
> tison.
>
> sebb <se...@gmail.com> 于2025年12月2日周二 08:39写道:
> >
> > The gradle.jar is included in the source repo [1]
> >
> > That does not seem right.
> >
> > Sebb
> > [1] https://github.com/apache/iggy/tree/4a9e215a4b6b1476daae8c4c3c34252b5162a240/foreign/java/gradle/wrapper
> >
> > On Mon, 1 Dec 2025 at 23:22, Justin Mclean <ju...@classsoftware.com> wrote:
> > >
> > > Hi,
> > >
> > > Having compiled code in a source release is not allowed by ASF policy [1], same for the issue with the LICENSE file [2]. I would suggest creating another RC.
> > >
> > > Kind Regards,
> > > Justin
> > >
> > > 1. https://www.apache.org/legal/release-policy.html#source-packages
> > > 2. https://www.apache.org/legal/release-policy.html#license-file
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by tison <wa...@gmail.com>.
Here is a solution to avoid bundling gradle.jar [1][2] in a source
distribution: like mvnw, download the binary if it is missing.

[1] https://github.com/apache/iceberg/blob/b35c7ec1b03e3897da68960cd556d635b2f5ae54/gradlew#L89-L91
[2] https://github.com/apache/kafka/blob/a7246ff13853d51c0005effbe4d277fc8c50e511/gradlew#L203-L234

They don't provide a version of gradlew.bat; instead, they delete it.
I hope Windows users will be fine since there is WSL now.

Best,
tison.

sebb <se...@gmail.com> 于2025年12月2日周二 08:39写道:
>
> The gradle.jar is included in the source repo [1]
>
> That does not seem right.
>
> Sebb
> [1] https://github.com/apache/iggy/tree/4a9e215a4b6b1476daae8c4c3c34252b5162a240/foreign/java/gradle/wrapper
>
> On Mon, 1 Dec 2025 at 23:22, Justin Mclean <ju...@classsoftware.com> wrote:
> >
> > Hi,
> >
> > Having compiled code in a source release is not allowed by ASF policy [1], same for the issue with the LICENSE file [2]. I would suggest creating another RC.
> >
> > Kind Regards,
> > Justin
> >
> > 1. https://www.apache.org/legal/release-policy.html#source-packages
> > 2. https://www.apache.org/legal/release-policy.html#license-file
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by sebb <se...@gmail.com>.
The gradle.jar is included in the source repo [1]

That does not seem right.

Sebb
[1] https://github.com/apache/iggy/tree/4a9e215a4b6b1476daae8c4c3c34252b5162a240/foreign/java/gradle/wrapper

On Mon, 1 Dec 2025 at 23:22, Justin Mclean <ju...@classsoftware.com> wrote:
>
> Hi,
>
> Having compiled code in a source release is not allowed by ASF policy [1], same for the issue with the LICENSE file [2]. I would suggest creating another RC.
>
> Kind Regards,
> Justin
>
> 1. https://www.apache.org/legal/release-policy.html#source-packages
> 2. https://www.apache.org/legal/release-policy.html#license-file

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

Having compiled code in a source release is not allowed by ASF policy [1], same for the issue with the LICENSE file [2]. I would suggest creating another RC. 

Kind Regards,
Justin

1. https://www.apache.org/legal/release-policy.html#source-packages
2. https://www.apache.org/legal/release-policy.html#license-file

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

Posted by "Kranti K. Parisa" <kr...@gmail.com>.
Looks like we have a bunch of +1 votes for the source distribution based release.

We plan to do a minor release with a few changes, can we incorporate Justin's feedback then or we need to fix them now and reinitiate this voting thread?

Best,
Kranti

> On Dec 1, 2025, at 10:45 PM, sebb <se...@gmail.com> wrote:
> There is another aspect to dependencies:
> 
> products can depend on category-X licensed code, provided that the
> dependency is optional:
> 
> https://apache.org/legal/resolved.html#optional
> 
> Of course, neither the source nor binary releases can contain cat-X
> code; it is up to the user to provide it.
> 
> On Mon, 1 Dec 2025 at 16:17, Piotr Gankiewicz <pi...@apache.org> wrote:
>> 
>>> Reverting my vote to -1 (binding) for the binary distribution for the
>>> reasons mentioned earlier in the thread (source distribution is OK).
>> 
>> Could you please elaborate on the binary distribution part (I wrote it a few comments back), as we only publish the source distribution? All the mentioned issues with some jar binary in the repository or missing headers etc. were resolved already, but before I will create an rc2 artifact, I just wanted to make sure that it's all ok.
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org

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

Posted by "Kranti K. Parisa" <kr...@gmail.com>.
Looks like we have a bunch of +1 votes for the source distribution based release.

We plan to do a minor release with a few changes, can we incorporate Justin's feedback then or we need to fix them now and reinitiate this voting thread?

Best,
Kranti

> On Dec 1, 2025, at 10:45 PM, sebb <se...@gmail.com> wrote:
> There is another aspect to dependencies:
> 
> products can depend on category-X licensed code, provided that the
> dependency is optional:
> 
> https://apache.org/legal/resolved.html#optional
> 
> Of course, neither the source nor binary releases can contain cat-X
> code; it is up to the user to provide it.
> 
> On Mon, 1 Dec 2025 at 16:17, Piotr Gankiewicz <pi...@apache.org> wrote:
>> 
>>> Reverting my vote to -1 (binding) for the binary distribution for the
>>> reasons mentioned earlier in the thread (source distribution is OK).
>> 
>> Could you please elaborate on the binary distribution part (I wrote it a few comments back), as we only publish the source distribution? All the mentioned issues with some jar binary in the repository or missing headers etc. were resolved already, but before I will create an rc2 artifact, I just wanted to make sure that it's all ok.
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by sebb <se...@gmail.com>.
There is another aspect to dependencies:

products can depend on category-X licensed code, provided that the
dependency is optional:

https://apache.org/legal/resolved.html#optional

Of course, neither the source nor binary releases can contain cat-X
code; it is up to the user to provide it.

On Mon, 1 Dec 2025 at 16:17, Piotr Gankiewicz <pi...@apache.org> wrote:
>
> > Reverting my vote to -1 (binding) for the binary distribution for the
> > reasons mentioned earlier in the thread (source distribution is OK).
>
> Could you please elaborate on the binary distribution part (I wrote it a few comments back), as we only publish the source distribution? All the mentioned issues with some jar binary in the repository or missing headers etc. were resolved already, but before I will create an rc2 artifact, I just wanted to make sure that it's all ok.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by Piotr Gankiewicz <pi...@apache.org>.
> Reverting my vote to -1 (binding) for the binary distribution for the
> reasons mentioned earlier in the thread (source distribution is OK).

Could you please elaborate on the binary distribution part (I wrote it a few comments back), as we only publish the source distribution? All the mentioned issues with some jar binary in the repository or missing headers etc. were resolved already, but before I will create an rc2 artifact, I just wanted to make sure that it's all ok.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Reverting my vote to -1 (binding) for the binary distribution for the
reasons mentioned earlier in the thread (source distribution is OK).

Regards
JB

On Mon, Dec 1, 2025 at 5:08 PM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:

> +1 (binding)
>
> I checked:
> - source distribution
> -- signature and checksum are good
> -- incubating is in the name/version
> -- DISCLAIMER is present
> -- LICENSE and NOTICE look good (DEPENDENCIES.md is used for binary
> artifact I guess, no need to mention in the NOTICE of the source
> distribution, but OK)
> -- A bunch of files doesn't have ASF header but OK
> -- No binary file found in the source distribution
>
> Regards
> JB
>
> On Thu, Nov 27, 2025 at 7:02 PM Piotr Gankiewicz <
> piotr.gankiewicz@gmail.com> wrote:
>
>> Hello everyone,
>>
>> This is the third 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/1wn8fyoo5m0x3h546q5xt7v7ox4n3fbj
>>
>> The vote PASSED with:
>> - 12 +1 votes (6 binding PPMC, 6 non-binding)
>> - 0 -1 votes
>>
>> *Vote Summary Thread:*
>> https://lists.apache.org/thread/lq8025x8q3ss6rc3d7yo4nvoqlyf9k34
>>
>> *The release candidate:*
>> https://dist.apache.org/repos/dist/dev/incubator/iggy/0.6.0/
>>
>> *Git commit for the release:*
>>
>> https://github.com/apache/iggy/commit/4a9e215a4b6b1476daae8c4c3c34252b5162a240
>>
>> *Change log for this release:*
>> https://github.com/apache/iggy/compare/server-0.5.0...server-0.6.0-rc.1
>>
>> *Git tag for the release candidate:*
>> https://github.com/apache/iggy/releases/tag/server-0.6.0-rc.1
>>
>> The artifacts were signed with PGP key 24A4364E, corresponding to
>> piotr@apache.org, 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.6.0-rc.1`
>> 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:
>>
>> MacOS:
>>
>>
>> 3807266d44b1b5ac552479b37cb9c2974b948fe78adfc02ec9b8822fabcdc37892a00b7a1e1fe5d891b2075165b1409981185cc9e900243cbd1c6aeec395801d
>>
>> Linux (Ubuntu)
>>
>>
>> ac8907bc14467162ee57f25061506376ee813c4398e26779d50a760aa82770efcf7fec91e0795f76c9b7c135ccf5a6ba27b813c093b9c9202f8830c8e7a9b12d
>>
>> 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,
>> Piotr Gankiewicz
>>
>

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

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1 (binding)

I checked:
- source distribution
-- signature and checksum are good
-- incubating is in the name/version
-- DISCLAIMER is present
-- LICENSE and NOTICE look good (DEPENDENCIES.md is used for binary
artifact I guess, no need to mention in the NOTICE of the source
distribution, but OK)
-- A bunch of files doesn't have ASF header but OK
-- No binary file found in the source distribution

Regards
JB

On Thu, Nov 27, 2025 at 7:02 PM Piotr Gankiewicz <pi...@gmail.com>
wrote:

> Hello everyone,
>
> This is the third 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/1wn8fyoo5m0x3h546q5xt7v7ox4n3fbj
>
> The vote PASSED with:
> - 12 +1 votes (6 binding PPMC, 6 non-binding)
> - 0 -1 votes
>
> *Vote Summary Thread:*
> https://lists.apache.org/thread/lq8025x8q3ss6rc3d7yo4nvoqlyf9k34
>
> *The release candidate:*
> https://dist.apache.org/repos/dist/dev/incubator/iggy/0.6.0/
>
> *Git commit for the release:*
>
> https://github.com/apache/iggy/commit/4a9e215a4b6b1476daae8c4c3c34252b5162a240
>
> *Change log for this release:*
> https://github.com/apache/iggy/compare/server-0.5.0...server-0.6.0-rc.1
>
> *Git tag for the release candidate:*
> https://github.com/apache/iggy/releases/tag/server-0.6.0-rc.1
>
> The artifacts were signed with PGP key 24A4364E, corresponding to
> piotr@apache.org, 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.6.0-rc.1`
> 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:
>
> MacOS:
>
>
> 3807266d44b1b5ac552479b37cb9c2974b948fe78adfc02ec9b8822fabcdc37892a00b7a1e1fe5d891b2075165b1409981185cc9e900243cbd1c6aeec395801d
>
> Linux (Ubuntu)
>
>
> ac8907bc14467162ee57f25061506376ee813c4398e26779d50a760aa82770efcf7fec91e0795f76c9b7c135ccf5a6ba27b813c093b9c9202f8830c8e7a9b12d
>
> 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,
> Piotr Gankiewicz
>

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

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

BTW, I just used rat [1] to find those issues, while its output can be noisy, it is good at picking up issues like these.

Kind Regards,
Justin

1. https://creadur.apache.org/rat/

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

Posted by Piotr Gankiewicz <pi...@apache.org>.

On 2025/12/01 13:22:02 tison wrote:
> While it's not required, in OpenDAL, we take a best effort to deliver
> a DEPENDENCIES file [1] to inform users what happens (mainly
> transitive deps) when they are depending on OpenDAL.
> 
> Besides, IIRC Iggy would produce a binary application at some point.
> When you release that binary bundle, you need to include the
> corresponding LICENSE and NOTICE files for all transitive deps since
> they are included in the bundle then.
> 
> [1] https://github.com/apache/opendal/blob/main/core/DEPENDENCIES.rust.tsv
> 
> Best,
> tison.
> 

Yes, we have the similar dependencies file in our repo e.g. https://raw.githubusercontent.com/apache/iggy/refs/heads/master/DEPENDENCIES.md

We do publish images to docker hub, but I'm not sure if it's related in any way to the mentioned licenses info for the source release distribution?

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by Piotr Gankiewicz <pi...@apache.org>.
On 2025/12/01 13:23:16 tison wrote:
> As a reference, you can take a look at Flink's distribution [1] for
> how they handle licenses differently between a source release and a
> binary release.
> 
> [1] https://dist.apache.org/repos/dist/release/flink/flink-2.1.1/

Thank you for the link, but as I wrote, we don't do the binary distribution, only the source one.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by tison <wa...@gmail.com>.
As a reference, you can take a look at Flink's distribution [1] for
how they handle licenses differently between a source release and a
binary release.

[1] https://dist.apache.org/repos/dist/release/flink/flink-2.1.1/

Best,
tison.

tison <wa...@gmail.com> 于2025年12月1日周一 21:22写道:
>
> While it's not required, in OpenDAL, we take a best effort to deliver
> a DEPENDENCIES file [1] to inform users what happens (mainly
> transitive deps) when they are depending on OpenDAL.
>
> Besides, IIRC Iggy would produce a binary application at some point.
> When you release that binary bundle, you need to include the
> corresponding LICENSE and NOTICE files for all transitive deps since
> they are included in the bundle then.
>
> [1] https://github.com/apache/opendal/blob/main/core/DEPENDENCIES.rust.tsv
>
> Best,
> tison.
>
> Piotr Gankiewicz <pi...@apache.org> 于2025年12月1日周一 21:17写道:
> >
> > > What matters is what is bundled in the source release; the license files need to reflect that, and not your dependencies, again see [1]
> >
> > Ok, so given that the source release is just a source code which references external libraries from the packages managers such as mvn, crates, nuget etc. we don't need to include any external licenses like e.g. BSD 3-Clause for passterm library referenced from crates.io, since it's the source distribution? At least that's my understanding, but wanted to confirm this, before the next rc2 release thread :)
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by tison <wa...@gmail.com>.
While it's not required, in OpenDAL, we take a best effort to deliver
a DEPENDENCIES file [1] to inform users what happens (mainly
transitive deps) when they are depending on OpenDAL.

Besides, IIRC Iggy would produce a binary application at some point.
When you release that binary bundle, you need to include the
corresponding LICENSE and NOTICE files for all transitive deps since
they are included in the bundle then.

[1] https://github.com/apache/opendal/blob/main/core/DEPENDENCIES.rust.tsv

Best,
tison.

Piotr Gankiewicz <pi...@apache.org> 于2025年12月1日周一 21:17写道:
>
> > What matters is what is bundled in the source release; the license files need to reflect that, and not your dependencies, again see [1]
>
> Ok, so given that the source release is just a source code which references external libraries from the packages managers such as mvn, crates, nuget etc. we don't need to include any external licenses like e.g. BSD 3-Clause for passterm library referenced from crates.io, since it's the source distribution? At least that's my understanding, but wanted to confirm this, before the next rc2 release thread :)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by Piotr Gankiewicz <pi...@apache.org>.
> What matters is what is bundled in the source release; the license files need to reflect that, and not your dependencies, again see [1]

Ok, so given that the source release is just a source code which references external libraries from the packages managers such as mvn, crates, nuget etc. we don't need to include any external licenses like e.g. BSD 3-Clause for passterm library referenced from crates.io, since it's the source distribution? At least that's my understanding, but wanted to confirm this, before the next rc2 release thread :)

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

>> So, two things here: the license files need to state what is contained in the source release, external dependencies are mostly irrelevant, but if 3rd party code is in the source artifact, it needs to be mentioned in the license file. The notice file is generally for items not mentioned in the license file and is unrelated to licensing. See [1].
> 
> Does it mean that as long as we use the external dependencies (rust crates, java libs etc.) in our source code (referenced by the projects), without actually embedding directly to repository some 3rd party source code, there's no need in our cases for these additional license files, and we can remove the current ./licenses directory?

What matters is what is bundled in the source release; the license files need to reflect that, and not your dependencies, again see [1]

Kind Regards,
Justin

1. https://infra.apache.org/licensing-howto.html#guiding

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

Posted by Piotr Gankiewicz <pi...@apache.org>.
> So, two things here: the license files need to state what is contained in the source release, external dependencies are mostly irrelevant, but if 3rd party code is in the source artifact, it needs to be mentioned in the license file. The notice file is generally for items not mentioned in the license file and is unrelated to licensing. See [1]. 

Does it mean that as long as we use the external dependencies (rust crates, java libs etc.) in our source code (referenced by the projects), without actually embedding directly to repository some 3rd party source code, there's no need in our cases for these additional license files, and we can remove the current ./licenses directory?

All the other remarks we've already fixed. Should we now proceed to rc2 artifact, start the new voting (phase 1), and then once passed, initiate once again the voting (phase 2) on general incubator list?

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

> We have mentioned in NOTICE that under DEPENDENCIES file we keep track of all the deps. While some of them might use e.g. BSD-3 -Clause or similar (like passterm), we added these also to licenses directory. However, we only use them as libraries (not binaries) in our source code - in such a case, do we need anything else than the dependencies file (e.g. could we remove the licenses directory)?

So, two things here: the license files need to state what is contained in the source release, external dependencies are mostly irrelevant, but if 3rd party code is in the source artifact, it needs to be mentioned in the license file. The notice file is generally for items not mentioned in the license file and is unrelated to licensing. See [1]. 

> By these 3rd party files do you have in mind the ones you listed from ./foreign/java directory?

Yes.

>> - One unexpected binary file [1]
> 
> Regarding the additional files in ./foreign/java, since we mostly use them to build our Java SDK library, should they even be
> part of the release artifact? And whether these are part of  the release or not, do we need to include either in LICENSE file or under ./licenses directory the info about gradle-wrapper.jar being used (it's the only jar file to be mentioned, correct)?

A source release cannot contain compiled code; there should be no jars in it, but someone should be able to easily compile the source release. Yes, it’s the only jar file included.

Kind Regards,
Justin

1. https://infra.apache.org/licensing-howto.html


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

Posted by Piotr Gankiewicz <pi...@apache.org>.
Hey Justin,
Thank you for the validation. Just wanted to ask about the following:

> - There seems to be a minor LICENSE issue in that you have come 3rd party licenses under "./licenses", but they are not mentioned in LICENSE. Is this 3rd party code included in the source release?

We have mentioned in NOTICE that under DEPENDENCIES file we keep track of all the deps. While some of them might use e.g. BSD-3 -Clause or similar (like passterm), we added these also to licenses directory. However, we only use them as libraries (not binaries) in our source code - in such a case, do we need anything else than the dependencies file (e.g. could we remove the licenses directory)?

> - There are several 3rd party files that should be mentioned in LICENSE [2]

By these 3rd party files do you have in mind the ones you listed from ./foreign/java directory?

> - One unexpected binary file [1]

Regarding these additional files in ./foreign/java - since we mostly use them to prepare our Java SDK library, should these even be a part of the release artifact? And whether these are part of  the release or not, do we need to include either in LICENSE file or under ./licenses directory the info about gradle-wrapper.jar being used (it's the only jar file to be mentioned, correct)?

As for the missing ASF headers in some files or invalid MIT license under cpp that's obvious to fix.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

Sorry, it’s -1 (binding) from me, as the compiled jar is included in the source release. [1]

I checked:
- incubating in name
- checksums are fine
- DISCLAIMER exists
- There seems to be a minor LICENSE issue in that you have come 3rd party licenses under "./licenses", but they are not mentioned in LICENSE. Is this 3rd party code included in the source release?
- There are several 3rd party files that should be mentioned in LICENSE [2]
- This ./foreign/cpp/LICENSE says MIT License / Copyright (c) 2023 Iggy I assuem that needs to be updated or removed?
- NOTICE looks fine
- Several files under ./web/src/lib/components/ and   ./web/src/routes/ are misisng ASF headers
- One unexpected binary file [1]
- I didn't try to compile

Kind Regards,
Justin

1. ./foreign/java/gradle/wrapper/gradle-wrapper.jar
2. ./foreign/java/gradlew.bat
3. ./foreign/java/gradlew
4 ./foreign/cpp/cmake/modules/CodeCoverage.cmake
5 ./foreign/cpp/LICENSE
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by hulk <hu...@gmail.com>.
+1 (binding, IPMC)

I have checked:

- [x] Download Iggy is valid.
- [x] Checksums and PGP signatures are valid.
- [x] Source code distributions have correct names matching the current
release.
- [x] LICENSE and NOTICE files are correct.
- [x] No compiled archives bundled in source archive.

On Sun, 30 Nov 2025 at 05:00, Yonik Seeley <ys...@gmail.com> wrote:
>
> +1 to release (binding, IPMC)
>
> -Yonik
>
> On Thu, Nov 27, 2025 at 1:02 PM Piotr Gankiewicz <pi...@gmail.com>
> wrote:
>
> > Hello everyone,
> >
> > This is the third 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/1wn8fyoo5m0x3h546q5xt7v7ox4n3fbj
> >
> > The vote PASSED with:
> > - 12 +1 votes (6 binding PPMC, 6 non-binding)
> > - 0 -1 votes
> >
> > *Vote Summary Thread:*
> > https://lists.apache.org/thread/lq8025x8q3ss6rc3d7yo4nvoqlyf9k34
> >
> > *The release candidate:*
> > https://dist.apache.org/repos/dist/dev/incubator/iggy/0.6.0/
> >
> > *Git commit for the release:*
> >
> > https://github.com/apache/iggy/commit/4a9e215a4b6b1476daae8c4c3c34252b5162a240
> >
> > *Change log for this release:*
> > https://github.com/apache/iggy/compare/server-0.5.0...server-0.6.0-rc.1
> >
> > *Git tag for the release candidate:*
> > https://github.com/apache/iggy/releases/tag/server-0.6.0-rc.1
> >
> > The artifacts were signed with PGP key 24A4364E, corresponding to
> > piotr@apache.org, 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.6.0-rc.1`
> > 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:
> >
> > MacOS:
> >
> >
> > 3807266d44b1b5ac552479b37cb9c2974b948fe78adfc02ec9b8822fabcdc37892a00b7a1e1fe5d891b2075165b1409981185cc9e900243cbd1c6aeec395801d
> >
> > Linux (Ubuntu)
> >
> >
> > ac8907bc14467162ee57f25061506376ee813c4398e26779d50a760aa82770efcf7fec91e0795f76c9b7c135ccf5a6ba27b813c093b9c9202f8830c8e7a9b12d
> >
> > 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,
> > Piotr Gankiewicz
> >



-- 
Best Regards,
- Hulk Lin

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by Yonik Seeley <ys...@gmail.com>.
+1 to release (binding, IPMC)

-Yonik

On Thu, Nov 27, 2025 at 1:02 PM Piotr Gankiewicz <pi...@gmail.com>
wrote:

> Hello everyone,
>
> This is the third 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/1wn8fyoo5m0x3h546q5xt7v7ox4n3fbj
>
> The vote PASSED with:
> - 12 +1 votes (6 binding PPMC, 6 non-binding)
> - 0 -1 votes
>
> *Vote Summary Thread:*
> https://lists.apache.org/thread/lq8025x8q3ss6rc3d7yo4nvoqlyf9k34
>
> *The release candidate:*
> https://dist.apache.org/repos/dist/dev/incubator/iggy/0.6.0/
>
> *Git commit for the release:*
>
> https://github.com/apache/iggy/commit/4a9e215a4b6b1476daae8c4c3c34252b5162a240
>
> *Change log for this release:*
> https://github.com/apache/iggy/compare/server-0.5.0...server-0.6.0-rc.1
>
> *Git tag for the release candidate:*
> https://github.com/apache/iggy/releases/tag/server-0.6.0-rc.1
>
> The artifacts were signed with PGP key 24A4364E, corresponding to
> piotr@apache.org, 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.6.0-rc.1`
> 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:
>
> MacOS:
>
>
> 3807266d44b1b5ac552479b37cb9c2974b948fe78adfc02ec9b8822fabcdc37892a00b7a1e1fe5d891b2075165b1409981185cc9e900243cbd1c6aeec395801d
>
> Linux (Ubuntu)
>
>
> ac8907bc14467162ee57f25061506376ee813c4398e26779d50a760aa82770efcf7fec91e0795f76c9b7c135ccf5a6ba27b813c093b9c9202f8830c8e7a9b12d
>
> 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,
> Piotr Gankiewicz
>

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

Posted by "Kranti K. Parisa" <kr...@gmail.com>.
+1 (non-binding, Apache Iggy PPMC)

Best,
Kranti

> On Nov 28, 2025, at 5:07 PM, Xuanwo <xu...@apache.org> wrote:
> bring my +1 binding notes from iggy's dev list.
> 
> On Fri, Nov 28, 2025, at 02:02, Piotr Gankiewicz wrote:
>> Hello everyone,
>> 
>> This is the third 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/1wn8fyoo5m0x3h546q5xt7v7ox4n3fbj
>> 
>> The vote PASSED with:
>> - 12 +1 votes (6 binding PPMC, 6 non-binding)
>> - 0 -1 votes
>> 
>> *Vote Summary Thread:*
>> https://lists.apache.org/thread/lq8025x8q3ss6rc3d7yo4nvoqlyf9k34
>> 
>> *The release candidate:*
>> https://dist.apache.org/repos/dist/dev/incubator/iggy/0.6.0/
>> 
>> *Git commit for the release:*
>> https://github.com/apache/iggy/commit/4a9e215a4b6b1476daae8c4c3c34252b5162a240
>> 
>> *Change log for this release:*
>> https://github.com/apache/iggy/compare/server-0.5.0...server-0.6.0-rc.1
>> 
>> *Git tag for the release candidate:*
>> https://github.com/apache/iggy/releases/tag/server-0.6.0-rc.1
>> 
>> The artifacts were signed with PGP key 24A4364E, corresponding to
>> piotr@apache.org, 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.6.0-rc.1`
>> 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:
>> 
>> MacOS:
>> 
>> 3807266d44b1b5ac552479b37cb9c2974b948fe78adfc02ec9b8822fabcdc37892a00b7a1e1fe5d891b2075165b1409981185cc9e900243cbd1c6aeec395801d
>> 
>> Linux (Ubuntu)
>> 
>> ac8907bc14467162ee57f25061506376ee813c4398e26779d50a760aa82770efcf7fec91e0795f76c9b7c135ccf5a6ba27b813c093b9c9202f8830c8e7a9b12d
>> 
>> 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,
>> Piotr Gankiewicz
> 
> --
> Xuanwo
> 
> https://xuanwo.io/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org

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

Posted by "Kranti K. Parisa" <kr...@gmail.com>.
+1 (non-binding, Apache Iggy PPMC)

Best,
Kranti

> On Nov 28, 2025, at 5:07 PM, Xuanwo <xu...@apache.org> wrote:
> bring my +1 binding notes from iggy's dev list.
> 
> On Fri, Nov 28, 2025, at 02:02, Piotr Gankiewicz wrote:
>> Hello everyone,
>> 
>> This is the third 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/1wn8fyoo5m0x3h546q5xt7v7ox4n3fbj
>> 
>> The vote PASSED with:
>> - 12 +1 votes (6 binding PPMC, 6 non-binding)
>> - 0 -1 votes
>> 
>> *Vote Summary Thread:*
>> https://lists.apache.org/thread/lq8025x8q3ss6rc3d7yo4nvoqlyf9k34
>> 
>> *The release candidate:*
>> https://dist.apache.org/repos/dist/dev/incubator/iggy/0.6.0/
>> 
>> *Git commit for the release:*
>> https://github.com/apache/iggy/commit/4a9e215a4b6b1476daae8c4c3c34252b5162a240
>> 
>> *Change log for this release:*
>> https://github.com/apache/iggy/compare/server-0.5.0...server-0.6.0-rc.1
>> 
>> *Git tag for the release candidate:*
>> https://github.com/apache/iggy/releases/tag/server-0.6.0-rc.1
>> 
>> The artifacts were signed with PGP key 24A4364E, corresponding to
>> piotr@apache.org, 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.6.0-rc.1`
>> 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:
>> 
>> MacOS:
>> 
>> 3807266d44b1b5ac552479b37cb9c2974b948fe78adfc02ec9b8822fabcdc37892a00b7a1e1fe5d891b2075165b1409981185cc9e900243cbd1c6aeec395801d
>> 
>> Linux (Ubuntu)
>> 
>> ac8907bc14467162ee57f25061506376ee813c4398e26779d50a760aa82770efcf7fec91e0795f76c9b7c135ccf5a6ba27b813c093b9c9202f8830c8e7a9b12d
>> 
>> 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,
>> Piotr Gankiewicz
> 
> --
> Xuanwo
> 
> https://xuanwo.io/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


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

Posted by Xuanwo <xu...@apache.org>.
bring my +1 binding notes from iggy's dev list.

On Fri, Nov 28, 2025, at 02:02, Piotr Gankiewicz wrote:
> Hello everyone,
>
> This is the third 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/1wn8fyoo5m0x3h546q5xt7v7ox4n3fbj
>
> The vote PASSED with:
> - 12 +1 votes (6 binding PPMC, 6 non-binding)
> - 0 -1 votes
>
> *Vote Summary Thread:*
> https://lists.apache.org/thread/lq8025x8q3ss6rc3d7yo4nvoqlyf9k34
>
> *The release candidate:*
> https://dist.apache.org/repos/dist/dev/incubator/iggy/0.6.0/
>
> *Git commit for the release:*
> https://github.com/apache/iggy/commit/4a9e215a4b6b1476daae8c4c3c34252b5162a240
>
> *Change log for this release:*
> https://github.com/apache/iggy/compare/server-0.5.0...server-0.6.0-rc.1
>
> *Git tag for the release candidate:*
> https://github.com/apache/iggy/releases/tag/server-0.6.0-rc.1
>
> The artifacts were signed with PGP key 24A4364E, corresponding to
> piotr@apache.org, 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.6.0-rc.1`
> 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:
>
> MacOS:
>
> 3807266d44b1b5ac552479b37cb9c2974b948fe78adfc02ec9b8822fabcdc37892a00b7a1e1fe5d891b2075165b1409981185cc9e900243cbd1c6aeec395801d
>
> Linux (Ubuntu)
>
> ac8907bc14467162ee57f25061506376ee813c4398e26779d50a760aa82770efcf7fec91e0795f76c9b7c135ccf5a6ba27b813c093b9c9202f8830c8e7a9b12d
>
> 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,
> Piotr Gankiewicz

-- 
Xuanwo

https://xuanwo.io/

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org