+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 On Thu, 19 Dec 2024 at 11:56, Clint Wylie <cwy...@apache.org> wrote: > Hi all, > > I have created a build for Apache Druid 31.0.1, release > candidate 2. > > Thanks to everyone who has helped contribute to the release! You can read > the proposed release notes here: > https://github.com/apache/druid/issues/17534 > > The release candidate has been tagged in GitHub as > druid-31.0.1-rc2 (520482cb9638e452b0553595b4f29bb397a63758), > available here: > https://github.com/apache/druid/releases/tag/druid-31.0.1-rc2 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/31.0.1-rc2/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1079/ > > Staged druid.apache.org website documentation is available here: > https://druid.staged.apache.org/docs/31.0.1/design/index.html > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:31.0.1-rc2 > > artifact checksums > src: > > fdf9257ef2694f078837288d803b74ce8532f09404e69f902400efd2148b504912ba943c6b026d27730c3b5932b452b7c8516446ec49e95206bfd24938b4614c > bin: > > df7aee79f2ab490367e0bac209e269bcbaa3df39471605bb1f53e5ba5227277d21b6c6566ddfb3b0b253f145975960612f3c8e72e93d286a0d5549258bc384ac > docker: 42d0a076fc7298d84fb6851ee046e1493566e0b45a8ef4b4d2c3d774f18f78b9 > > 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-31.0.1-src.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-31.0.1-src.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-31.0.1-bin.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-31.0.1-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-31.0.1-src.tar.gz.asc \ > apache-druid-31.0.1-src.tar.gz > > gpg --verify apache-druid-31.0.0-bin.tar.gz.asc \ > apache-druid-31.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 31.0.1 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > For additional commands, e-mail: dev-h...@druid.apache.org > >
