+1 (binding) src package: * verified checksum and signature * LICENSE and NOTICE present * rat check passed * built release distribution successful, no compilation error or cve flagged * tested binary package built from source distribution with quickstart configuration with kafka ingestion, ran some queries
binary package: * verified checksum and signature * LICENSE and NOTICE present * tested with quickstart configuration with MSQ ingestion, ran some queries docker: * verified checksum * tested using example docker-compose from source distribution with JSON spec based batch ingestion, ran some queries On Mon, Aug 4, 2025 at 4:21 PM Lucas Capistrant <capistrant.lu...@gmail.com> wrote: > > Hi all, > > I have created a build for Apache Druid 34.0.0, release > candidate 2. > > Thanks for everyone who has helped contribute to the release! You can read > the proposed release notes here: > https://github.com/apache/druid/pull/18231 > > The release candidate has been tagged in GitHub as > druid-34.0.0-rc2 (aa107ecd801a1f1c31e9965ee020f2cea9bda613), > available here: > https://github.com/apache/druid/releases/tag/druid-34.0.0-rc2 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/34.0.0-rc2/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1089/ > > Staged druid.apache.org website documentation is available here: > https://druid.staged.apache.org/docs/34.0.0/design > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:34.0.0-rc2 > > artifact checksums > src: > 50334e3a7389315858971139efb1ffad9ed75eeaa68aabc3ee00d298035cf704cce4a55a2ae2cd23e7136de3c0c176aa0333a54376af5d69fc204e186c49b29a > bin: > 8a546ac0c5d477ba09192ee5935349bef24413ea7cd896f15c0f8ea42bae25aae1ec8ccec786baed276a38e4cb140416870ed698ab01856d94c98a8e2bf1f4b1 > docker: > sha256:ec2fc8ce308ad1d16e32e8de6693c59af7f1a8af9a4a839328edda230a37cf09 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/capistrant.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-34.0.0-src.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-34.0.0-src.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-34.0.0-bin.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-34.0.0-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-34.0.0-src.tar.gz.asc \ > apache-druid-34.0.0-src.tar.gz > > gpg --verify apache-druid-34.0.0-bin.tar.gz.asc \ > apache-druid-34.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 34.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! --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
