sure, we can wait for the 3 day Iggy voting. Best, Kranti
> On Dec 4, 2025, at 1:35 AM, PJ Fanning <[email protected]> wrote: > > I'm voting -1 binding just in case. > >> On Wed, 3 Dec 2025 at 21:04, PJ Fanning <[email protected]> wrote: >> >> Rules are rules. If you send an email saying the vote is 72 hrs, it >> lasts 72 hrs. Check the email for the vote. >> >>> On Wed, 3 Dec 2025 at 20:24, Kranti K. Parisa <[email protected]> >>> wrote: >>> >>> Hi PJ, >>> >>> We can certainly extend it to 3 days. However this is RC2 without any code >>> changes, primary addressing license files and other minor feedback from the >>> previous Incubator voting thread for 0.6.0 release. So Iggy community and >>> PPMC reviewed all changes in RC2 and we feel confident to send this to >>> Incubator voting. >>> >>> Best, >>> Kranti >>> >>>> On Dec 4, 2025, at 12:19 AM, PJ Fanning <[email protected]> wrote: >>>> >>>> The Iggy vote was not left open for 72hrs as far as I can see. >>>> >>>>> On Wed, 3 Dec 2025 at 19:27, Piotr Gankiewicz >>>>> <[email protected]> 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. It's the >>>>> continuation of rc1 voting, where we addressed all the required >>>>> improvements, and published the rc2 source release artifact. >>>>> >>>>> *Vote Thread:* >>>>> https://lists.apache.org/thread/fvjktho1b647yfzkmm5zwg52kh3cttxv >>>>> >>>>> The vote PASSED with: >>>>> - 10 +1 votes (5 binding PPMC, 5 non-binding) >>>>> - 0 -1 votes >>>>> >>>>> *Vote Summary Thread:* >>>>> https://lists.apache.org/thread/z4t0ph5v625cmwbyc5r01kn9ocfvnv9g >>>>> >>>>> *The release candidate:* >>>>> https://dist.apache.org/repos/dist/dev/incubator/iggy/0.6.0-rc2/ >>>>> >>>>> *Git commit for the release:* >>>>> https://github.com/apache/iggy/commit/90e4eab8c42f48303cb34f3fea29dce6f8d4158c >>>>> >>>>> *Change log for this release:* >>>>> https://github.com/apache/iggy/compare/server-0.5.0...server-0.6.0-rc.2 >>>>> >>>>> *Git tag for the release candidate:* >>>>> https://github.com/apache/iggy/releases/tag/server-0.6.0-rc.2 >>>>> >>>>> The artifacts were signed with PGP key 24A4364E, 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.6.0-rc.2` >>>>> 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: >>>>> >>>>> e6cec95a76322beb844ae2f04af9c29c29f0db9330b8e7547085d0e4e30b322e71e723fe4d7f2e28c2c99a5d344aa2f79fe9a12b7728060de1b89b581f4a4f9e >>>>> >>>>> Linux (Ubuntu) >>>>> >>>>> cf05bd7c111882879c29c1657e9c362b4a945c8d719c8bbc7f77f92972e2d0415ef3977708e06aab5fe5645e9002e403238d3cee9efbd740ac3b10c6eaff70f2 >>>>> >>>>> 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 >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
