+1 (binding)

✓ Downloaded all artifacts from
https://dist.apache.org/repos/dist/dev/druid/36.0.0-rc1/
✓ Verified GPG signatures for all artifacts
✓ Verified SHA512 checksums for all artifacts
✓ Verified LICENSE and NOTICE files in all artifacts
✓ Pulled Docker image apache/druid:36.0.0-rc1
✓ Ran the Docker based embedded-tests with this docker image
✓ RAT checks passed
✓ Built from source successfully
✓ Built Docker image apache/druid-vote:36.0.0-rc1 from the source build
artifacts
✓ Deployed Druid cluster on Kubernetes using built docker image
✓ Validated Druid cluster successfully on k8s (native ingest, msq insert,
native json queries, sql queries)


On Mon, Feb 2, 2026 at 2:32 PM Zoltan Haindrich <[email protected]> wrote:

> Hi all,
>
> I have created a build for Apache Druid 36.0.0, release candidate 1.
>
> Thanks for everyone who has helped contribute to the release! You can read
> the proposed release notes here:
> https://github.com/apache/druid/pull/18919
>
> The release candidate has been tagged in GitHub as
> druid-36.0.0-rc1(18ee9bce703ff13bf62094b07b1ebd9257225655),
> available here: https://github.com/apache/druid/tree/druid-36.0.0-rc1
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/druid/36.0.0-rc1/
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachedruid-1093
>
> Staged druid.apache.org website documentation is available here:
> https://druid.staged.apache.org/docs/36.0.0/
>
> A Docker image containing the binary of the release candidate can be
> retrieved via:
> docker pull apache/druid:36.0.0-rc1
>
> artifact checksums:
> apache-druid-36.0.0-bin.tar.gz
>
> f83b4e2f56e434a01553db3e9e8709cf0f962297f786ca6034106a9fc18689fa70b5f2ea7bd6b46d54f637e81c648f6528ded6e94cb91b21ea3823c18a64b140
>
> apache-druid-36.0.0-src.tar.gz
>
> d4f78b627e0c46db0d328ce53460ae3f5639831f20efc50ed6c25c5999aa310dd089d4d7813c0994f7c6714a2df24594ab7b14ab087e360bb2fbc5992e6e7293
>
> docker:
> sha256:528a78a68b1dde47a5984e60975203d8cdf0bd4f477f8b97b84a8b2b44e3c683
>
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/kgyrtkirk.asc
>
> This key and the key of other committers can also be found in the project's
> KEYS file here:
> https://dist.apache.org/repos/dist/release/druid/KEYS
>
> (If you are a committer, please feel free to add your own key to that file
> by following the instructions in the file's header.)
>
> Verify checksums:
> diff <(shasum -a512 apache-druid-36.0.0-src.tar.gz | cut -d ' ' -f1) <(cat
> apache-druid-36.0.0-src.tar.gz.sha512 ; echo)
> diff <(shasum -a512 apache-druid-36.0.0-bin.tar.gz | cut -d ' ' -f1) <(cat
> apache-druid-36.0.0-bin.tar.gz.sha512 ; echo)
>
> Verify signatures:
> gpg --verify apache-druid-36.0.0-src.tar.gz.asc
> apache-druid-36.0.0-src.tar.gz
> gpg --verify apache-druid-36.0.0-bin.tar.gz.asc
> apache-druid-36.0.0-bin.tar.gz
>
> Please review the proposed artifacts and vote. Note that Apache has
> specific requirements that must be met before +1 binding votes can be cast
> by PMC members. Please refer to the policy at
> http://www.apache.org/legal/release-policy.html#policy for more details.
>
> As part of the validation process, the release artifacts can be generated
> from source by running:
> mvn clean install -Papache-release,dist -Dgpg.skip
>
> The RAT license check can be run from source by:
> mvn apache-rat:check -Prat
>
> This vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Druid 0.17.0
> [ ] 0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> cheers,
> Zoltan
>

Reply via email to