+1 (binding) Source: - NOTICE and LICENSE present - Verified checksum and signature - Verified git.version file - mvn build with tests passed - mvn rat check passed - Ran druid cluster with the built binaries, ingested wiki data and verified using basic queries
Binary: - NOTICE and LICENSE present - Verified checksum and signature - Ran quickstart cluster and ingested wiki data and verified using basic queries Docker: - Verified checksum - Started up cluster using docker compose - Ran native ingestion and verified using basic queries Thanks for all the hard work in managing this release. On Wed, Jun 15, 2022 at 7:22 AM Abhishek Agarwal <abhishek.agar...@imply.io> wrote: > Hi all, > I have created a build for Apache Druid 0.23.0, release candidate 2. > > Thanks to everyone who has helped contribute to the release. You can read > the draft release notes here: > https://github.com/apache/druid/issues/12510 > > The release candidate has been tagged in GitHub as druid-0.23.0-rc2 > (c085dd1a5e3db02806f1fc8f54fd7f9297ee0f77), available here: > https://github.com/apache/druid/tree/druid-0.23.0-rc2 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/0.23.0-rc2/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1030 > > Staged druid.apache.org website documentation is available here: > https://druid.staged.apache.org/docs/0.23.0/design/index.html > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:0.23.0-rc2 > > artifact checksums > src: > > 50ff149fa274ac10c01040dc30bbf28fc24732da5a27f1b88f89b13bbee5c9ec8a68f5d57e7caabc5813cac5f551e1c4ca94dc8faa9c6d8efc022f3bd3bef7e3 > > bin: > > 5e7420bdc66247f0309fc0c1eafeff7ba935ed195f3a28c2da4b23a28ff637300b46b1c3d048379ccd570dde164968494ff5d8847e82eaf9b0edb518f8665328 > > docker (sha256): > ed9719968b4be3a2f1643907a1a5a5814e2ee1215f3604da8b2da2ac05f65912 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/abhishek > 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-0.23.0-src.tar.gz | cut -d ' ' -f1) <(cat > apache-druid-0.23.0-src.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-0.23.0-bin.tar.gz | cut -d ' ' -f1) <(cat > apache-druid-0.23.0-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-0.23.0-src.tar.gz.asc > apache-druid-0.23.0-src.tar.gz > > gpg --verify apache-druid-0.23.0-bin.tar.gz.asc > apache-druid-0.23.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 the source by running: > mvn clean install -Papache-release,dist -Dgpg.skip > > The RAT license check can be run from the 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.23.0 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > Thanks! >
