+1 (binding)
src package:
- verified signature/checksum
- LICENSE/NOTICE present
- built binary distribution,
- Ingested some data using MSQ and ran some
queries
- Tested Classic batch ingestion
- Tested Kafka ingestion locally
binary package:
- verified signature/checksum
- LICENSE/NOTICE present
- Ingested some data using MSQ and ran some
queries
- Tested Classic batch ingestion
- Tested Kafka ingestion locally
docker:
- verified checksum
- started cluster with docker-compose, tested MSQ ingestion and classic
batch ingestion
On Fri, Oct 18, 2024 at 7:05 PM Kashif Faraz <kfa...@apache.org> wrote:
> Hi
>
> I have created a build for Apache Druid 31.0.0, 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/17332
>
> The release candidate has been tagged in GitHub as
> druid-31.0.0-rc2 (de96f9ff75b0a473d52627e5aed33d1e49467969),
> available here:
> https://github.com/apache/druid/releases/tag/druid-31.0.0-rc2
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/druid/31.0.0-rc2/
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachedruid-1077/
>
> Staged druid.apache.org website documentation is available here:
> https://druid.staged.apache.org/docs/31.0.0/design/index.html
>
> A Docker image containing the binary of the release candidate can be
> retrieved via:
> docker pull apache/druid:31.0.0-rc2
>
> artifact checksums
> src:
>
> 12e23bd657b455d89741fc2db51d5bd6a2d75b946ad4e956ec84a654f4bd90b7c7073f770dcc47a21e1f2dab2d921173f151eabbae4d76ad85b9d26f8a3596bf
> bin:
>
> 831448a78a2d4a1872506636c4fd4d24ba0d618f02ba148bd99a2afc2fcb7f8d41fde4b9c93dbb4d117c5783313989f641bc91b63db71737645bfc94c0ec3f73
> docker: 51a3cddd60d0b7aca8bf73a3f0770e94f53dcd44548bdf6ea4d5007f8cf80314
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/kfaraz.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.0-src.tar.gz | \
> cut -d ' ' -f1) \
> <(cat apache-druid-31.0.0-src.tar.gz.sha512 ; echo)
>
> diff <(shasum -a512 apache-druid-31.0.0-bin.tar.gz | \
> cut -d ' ' -f1) \
> <(cat apache-druid-31.0.0-bin.tar.gz.sha512 ; echo)
>
> Verify signatures:
> gpg --verify apache-druid-31.0.0-src.tar.gz.asc \
> apache-druid-31.0.0-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.0
> [ ] 0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Thanks
> Kashif Faraz
>
