+1 *Source code*
- NOTICE and LICENSE files present - verified signatures and checksums - git.version file is present and correct - mvn build passed with unit tests - mvn rat checks passed - ran cluster with built binaries and ran native batch ingestion followed by basic queries *Binary* - NOTICE and LICENSE files present - Verified signatures and checksums - ran cluster with pre-packaged binaries and ran both native and kafka ingestion followed by basic queries *Docker* - verified checksum - started docker by docker-compose.xml - ran native ingestion and kafka ingestion followed by basic queries Thanks. On Thu, Sep 16, 2021 at 3:32 PM Clint Wylie <cwy...@apache.org> wrote: > Hi all, > > I have created a build for Apache Druid 0.22.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/11657 > > The release candidate has been tagged in GitHub as > druid-0.22.0-rc1 (cc603d6118cf7f14056744d608b93d4d8fd4e710), > available here: > https://github.com/apache/druid/releases/tag/druid-0.22.0-rc1 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/0.22.0-rc1/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1026/ > > Staged druid.apache.org website documentation is available here: > https://druid.staged.apache.org/docs/0.22.0/design/index.html > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:0.22.0-rc1 > > artifact checksums > src: > > 9073e4e4f1dedcddc7c644f11480ed5354093d3aff26986780e871b20b1bcfd64f9aafc7cc9e82aeb169c6534274aa3fa3f8710d53f3dd9c704ec32de7b2141d > bin: > > 6a2d191cda37e712a39e59066259f028fadf407a6b3f7a746908cd3c4ed10e6d43008778a045eefc551dbbc3e47f8c1cdbfaab44845fbc217d22029bc3b3c3de > docker: 626fd96a997361dce8452c68b28e935a2453153f0d743cf208a0b4355a4fc2c3 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/cwylie.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-0.22.0-src.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-0.22.0-src.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-0.22.0-bin.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-0.22.0-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-0.22.0-src.tar.gz.asc \ > apache-druid-0.22.0-src.tar.gz > > gpg --verify apache-druid-0.22.0-bin.tar.gz.asc \ > apache-druid-0.22.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.22.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 > >
