+1 (binding) src package: * verified checksum and signature * checked for LICENSE and NOTICE * rat check successful * built binary distribution * ran MSQ ingestion and demo MSQ queries on the dataset (using the built binary) * ran native ingestion and sample queries on the wikipedia dataset (using the built binary)
binary package: * verified checksum and signature * checked for LICENSE and NOTICE * ran MSQ ingestion and demo MSQ queries on the dataset * ran native ingestion and sample queries on the wikipedia dataset docker: * verified checksum * ran druid cluster from the docker image * ran native ingestion and sample queries on the wikipedia dataset On Sat, 8 Jun 2024 at 15:58, Adarsh Sanjeev <adarshsanj...@apache.org> wrote: > Hi all, > > I have created a build for Apache Druid 30.0.0, release candidate 3. > > Thanks to everyone who has helped contribute to the release! You can read > the proposed release notes here: > https://github.com/apache/druid/issues/16505 > > The release candidate has been tagged in GitHub as druid-30.0.0-rc3 > (09d36ee324747f1407705c27618b6d415c3fa8a9), available here: > https://github.com/apache/druid/releases/tag/druid-30.0.0-rc3 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/30.0.0-rc3/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1066/ > > Staged druid.apache.org website documentation is available here: > https://druid.staged.apache.org/docs/30.0.0/design/index.html > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:30.0.0-rc3 > > artifact checksums > src: > > 87e145684a646667811ab7db9f812b13bf78a4bafb23d407853f9dd3fbbbd0f523a1a0d12aeed67543f9e1e462c41c7cde6f7420319bffe5f564119464d83e09 > bin: > > fe50f134e4c2bba2bf04e0f5ddba1886af1c7ed8a6b4e361347efc853ef50aba8e35b664af0531cdabce69c6063fff0913d2165ae160614730912698f35aee83 > docker: 978d9380fb6fcab79cafc6c53f11edbb6e80a664481e843d6fe069b1fd05f129 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/adarshsanjeev.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-30.0.0-src.tar.gz | cut -d ' ' -f1) <(cat > apache-druid-30.0.0-src.tar.gz.sha512 ; echo) > diff <(shasum -a512 apache-druid-30.0.0-bin.tar.gz | cut -d ' ' -f1) <(cat > apache-druid-30.0.0-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-30.0.0-src.tar.gz.asc > apache-druid-30.0.0-src.tar.gz > gpg --verify apache-druid-30.0.0-bin.tar.gz.asc > apache-druid-30.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 30.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! >
