The KEYS address should be https://downloads.apache.org/incubator/iggy/KEYS
This is a requirement in votes. Please don't use the dev area of dist.apache.org for KEYS. The release area of dist.apache.org is automatically copied over to downloads.apache.org. On 2025/12/02 17:43:40 "spetz (via GitHub)" wrote: > > GitHub user spetz created a discussion: [VOTE] Release Apache Iggy > (incubating) v0.6.0 > > Hello, Apache Iggy (incubating) Community, > > This is a call for a vote to release Apache Iggy (incubating) version 0.6.0 > > It's the continuation of the previous voting thread (rc1), as we found a few > minor issues that had to be fixed accordingly, hence the rc2 source release > artifact was created. > > Along with the Iggy Server 0.6.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: > https://github.com/apache/iggy/commit/90e4eab8c42f48303cb34f3fea29dce6f8d4158c > > The change lists about this release: > > https://github.com/apache/iggy/compare/server-0.5.0...server-0.6.0-rc.2 > > Git tag for the release: > > https://github.com/apache/iggy/releases/tag/server-0.6.0-rc.2 > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/iggy/0.6.0-rc2/ > > 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: > > MacOS > > ``` > e6cec95a76322beb844ae2f04af9c29c29f0db9330b8e7547085d0e4e30b322e71e723fe4d7f2e28c2c99a5d344aa2f79fe9a12b7728060de1b89b581f4a4f9e > ``` > > Linux (Ubuntu) > > ``` > cf05bd7c111882879c29c1657e9c362b4a945c8d719c8bbc7f77f92972e2d0415ef3977708e06aab5fe5645e9002e403238d3cee9efbd740ac3b10c6eaff70f2 > ``` > > ### Build and test > > To build, you need to have [Rust](https://www.rust-lang.org/tools/install) > installed. > > Then, simply type `cargo build` and next `cargo test` to ensure that > everything does work as expected. > > Thanks, > Piotr Gankiewicz > > GitHub link: https://github.com/apache/iggy/discussions/2435 > > ---- > This is an automatically sent email for [email protected]. > To unsubscribe, please send an email to: [email protected] > >
