+1 (binding) Src package - license and notice present - verified signature - verified checksum - rat checks passed - built dist from source - ran dist from source build in docker with druid-operator - validated k8s extensions - ingested with native batch and msq - queried with sql, native, and msq select
Binary package - license and notice present - verified signature - verified checksum Docker - ran docker embedded tests - ran in Druid operator - validated k8s extensions - ingested with native batch and msq - queried with sql, native, and msq select On Tue, Oct 28, 2025 at 4:33 PM Cece Mei <[email protected]> wrote: > Hi all, > > I have created a build for Apache Druid 35.0.0, release candidate 1. > > Thanks to everyone who has helped contribute to the release! You can read > the proposed release notes here: > https://github.com/apache/druid/issues/18630 > > The release candidate has been tagged in GitHub as druid-35.0.0-rc1 > (f6712c6694a2b95961607c3ceac0123418641d40), > available here: > https://github.com/apache/druid/releases/tag/druid-35.0.0-rc1 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/35.0.0-rc1/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1091/ > > Staged druid.apache.org website documentation is available here: > https://druid.staged.apache.org/docs/35.0.0/design/index.html > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:35.0.0-rc1 > > artifact checksums > src: > > 831c273d3c9806d2e73a8f216a29b33a4a10eed12f812258b01d0d1cb063d96806b420cd758dda8641beaf7e813855dafb676bfb1c706391a69ad524a16fe45c > bin: > > 28d9efef40d3e9e4328694bbb9fb449f19470b77c859d3cf83a0e475b6bd5f0dd0e8c9fe596e0801cf9105f2daf424ed3f136b9209d70a434bc6b43dc4d441cf > docker: > 1c48677ee8a8dc633edcc5f2b29393a09b35d0e5f065cf2863872c02c47485b3 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/yqm.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-35.0.0-src.tar.gz | cut -d ' ' -f1) \ > <(cat apache-druid-35.0.0-src.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-35.0.0-bin.tar.gz | cut -d ' ' -f1) \ > <(cat apache-druid-35.0.0-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-35.0.0-src.tar.gz.asc > apache-druid-35.0.0-src.tar.gz > > gpg --verify apache-druid-35.0.0-bin.tar.gz.asc > apache-druid-35.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 > https://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 35.0.0 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > Thanks! >
