+1 (binding) For the release note, I left a comment: https://github.com/apache/druid/pull/17872
The checked items are as follows: src package: * verified checksum and signature * checked for LICENSE and NOTICE * rat check successful * built binary distribution, ran native ingestion and some queries binary package: * verified checksum and signature * checked for LICENSE and NOTICE docker: * verified checksum * used the docker image to upgrade a test cluster in K8S from Druid 27, ran native ingestion under the MM-less mode, ran some queries On Fri, Apr 18, 2025 at 3:32 PM Zoltan Haindrich <k...@rxd.hu> wrote: > Hi all, > > I have created a build for Apache Druid 33.0.0, release candidate 3. > changes compared to rc2: > - a comment on druid.host so that upgrade of druid-helm is smoother [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/17872 > > The release candidate has been tagged in GitHub as druid-33.0.0-rc3 > (84b59b984b69ebc34e0c971ad207b69384941c0b), > available here: https://github.com/apache/druid/tree/druid-33.0.0-rc3 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/33.0.0-rc3/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1087 > > Staged druid.apache.org website documentation is available here: > https://druid.staged.apache.org/docs/33.0.0/ > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:33.0.0-rc3 > > artifact checksums: > 33.0.0-rc3/apache-druid-33.0.0-bin.tar.gz > > 353d72186d898c8c63c276bbcb77f5ce4a96212c8a540a0040ffd663064a4e2ae381099981e1e218907907168077fe536dc0441045e1bac1ba5ef46db9856875 > > 33.0.0-rc3/apache-druid-33.0.0-src.tar.gz > > 2e704810f9720522461cf9ef8a9e804de29e025026b91882c6489f9830dd7533f1896edf2647374e1fa7d92d9fb378c384a3c2cec26991a3a8b52df4e6428436 > > docker: > sha256:6f5e1abe4dca1eb4ec5162a77ff884799ffb8dd8f9aa0c774eee15499ec4a9a6 > > 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-33.0.0-src.tar.gz | cut -d ' ' -f1) <(cat > apache-druid-33.0.0-src.tar.gz.sha512 ; echo) > diff <(shasum -a512 apache-druid-33.0.0-bin.tar.gz | cut -d ' ' -f1) <(cat > apache-druid-33.0.0-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-33.0.0-src.tar.gz.asc > apache-druid-33.0.0-src.tar.gz > gpg --verify apache-druid-33.0.0-bin.tar.gz.asc > apache-druid-33.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 > > [1] https://github.com/asdf2014/druid-helm >
