+1 (binding) src package: - verified signature/hash - LICENSE and NOTICE are present - unit tests - built binary distribution - ran the Kafka ingestion tutorial - ran some batch tasks
bin package: - verified signature/hash - LICENSE and NOTICE are present - ran the Kafka ingestion tutorial - ran some batch tasks docker: - verified checksum - started a cluster with docker-compose On Mon, Jul 13, 2020 at 6:35 PM Clint Wylie <cwy...@apache.org> wrote: > Hi all, > > I have created a build for Apache Druid 0.19.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/10139 > > The release candidate has been tagged in GitHub as > druid-0.19.0-rc1 (c557a1448d872e3aab03aec3bafb035e74583656), > available here: > https://github.com/apache/druid/releases/tag/druid-0.19.0-rc1 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/0.19.0-rc1/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1018/ > > Staged druid.apache.org website documentation is available here: > https://druid.staged.apache.org/docs/0.19.0/design/index.html > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:0.19.0-rc1 > > artifact checksums > src: > > c6e9d4e38f371989ec89f745ae5c6b8c8bfe78a8abd89ee6013f53bf19a39f0c34d7e3e077d15b083cfad472d7f12b9466bcc2a05e786dbecbcd428ce3be85f0 > bin: > > 24dce0d5fad8be7608c0cd3cee183e43ac1bc63b5139fc7ef8e37207937825ca999f488224834d4265213051b8e3eb84186fba4b665cf9c98d1f97a02cf1764b > docker: 233db3b3397c6a28e69afb0d29ed698ea39f10d360c834526a0d76a5b510cc21 > > 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.19.0-src.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-0.19.0-src.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-0.19.0-bin.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-0.19.0-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-0.19.0-src.tar.gz.asc \ > apache-druid-0.19.0-src.tar.gz > > gpg --verify apache-druid-0.19.0-bin.tar.gz.asc \ > apache-druid-0.19.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.19.0 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > Thanks! >
