Thanks Clint, I will cancel this vote. On Wed, Apr 15, 2020 at 3:30 PM Clint Wylie <cwy...@apache.org> wrote:
> -1 (binding) > > It looks like there are some extra code coverage analysis results in the > source package in apache-druid-0.18.0-src/web-console/coverage/ which is > causing this command to fail: > > mvn apache-rat:check -Prat > > since these files have no license information. > > On Wed, Apr 15, 2020 at 2:52 PM Jihoon Son <jihoon...@apache.org> wrote: > > > Hi all, > > > > I have created a build for Apache Druid 0.18.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/issues/9652 > > > > The release candidate has been tagged in GitHub as > > druid-0.18.0-rc2 (3280d14ba523d0b6d623e73945201980e48c8238), > > available here: > > https://github.com/apache/druid/releases/tag/druid-0.18.0-rc2 > > > > The artifacts to be voted on are located here: > > https://dist.apache.org/repos/dist/dev/druid/0.18.0-rc2/ > > > > Staged druid.apache.org website documentation is available here: > > https://druid.staged.apache.org/docs/0.18.0/design/index.html > > > > A Docker image containing the binary of the release candidate can be > > retrieved via: > > docker pull apache/druid:0.18.0-rc2 > > > > artifact checksums > > src: > > > > > 4b20047f715b03aa8d5fd0d7eac9e7cc4caa3883c538ae0cde5de0777136e687bb7ce05f7b07aaf9815e1b93cd95fd6e04ab2c64c5d7a11beff72528611018b5 > > bin: > > > > > a95faa297dab5501a98c4e1d34593eddb052652f1c2b77245b44f155d9ea355c5a4a856afb65f53daa6660ef67a8372dd802f728d3ca0869095301ab822e3545 > > docker: 812ae45f1226c146300d04a7b1096e4a9470c78c90548b4645bf28275f840a6c > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/jihoonson.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.18.0-src.tar.gz | \ > > cut -d ' ' -f1) \ > > <(cat apache-druid-0.18.0-src.tar.gz.sha512 ; echo) > > > > diff <(shasum -a512 apache-druid-0.18.0-bin.tar.gz | \ > > cut -d ' ' -f1) \ > > <(cat apache-druid-0.18.0-bin.tar.gz.sha512 ; echo) > > > > Verify signatures: > > gpg --verify apache-druid-0.18.0-src.tar.gz.asc \ > > apache-druid-0.18.0-src.tar.gz > > > > gpg --verify apache-druid-0.18.0-bin.tar.gz.asc \ > > apache-druid-0.18.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.18.0 > > [ ] 0 I don't feel strongly about it, but I'm okay with the release > > [ ] -1 Do not release this package because... > > > > Thanks! > > >
