+1

src
- verified .asc signatures and .sha512 checksums
- LICENSE/NOTICE present
- compiled, ran the license check/unit tests
- started nano-quickstart cluster and ran both native ingestion and Kafka
ingestion followed by some basic queries

bin
- verified .asc signatures and .sha512 checksums verified
- LICENSE/NOTICE present
- started nano-quickstart cluster and ran both native ingestion and Kafka
ingestion

docker
- started docker on Linux(CentOS) and ran both native ingestion and Kafka
ingestion followed by some basic queries
- started docker on macOS and ran both native ingestion and Kafka ingestion
followed by some basic queries


Clint Wylie <cwy...@apache.org> 于2021年6月3日周四 下午5:00写道:

> Hi all,
>
> I have created a build for Apache Druid 0.21.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/11249
>
> The release candidate has been tagged in GitHub as
> druid-0.21.1-rc2 (6ba6b16786eca5a25ebad2f00df4b2a265861b01),
> available here:
> https://github.com/apache/druid/releases/tag/druid-0.21.1-rc2
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/druid/0.21.1-rc2/
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachedruid-1025/
>
> Staged druid.apache.org website documentation is available here:
> https://druid.staged.apache.org/docs/0.21.1/design/index.html
>
> A Docker image containing the binary of the release candidate can be
> retrieved via:
> docker pull apache/druid:0.21.1-rc2
>
> artifact checksums
> src:
>
> 65eff0c302c316afbf4a84c61a9f54a1baf5ff3cd1baf390d9034665f7e4fbc7457e108c8c5a4ac66350ee69d922e5bcdacde14abac4b54398378b99022acd16
> bin:
>
> a68c63ddf92a0939315bd8b79fbdd5fae712e888d1a0e0466f0a87a8e8f1270d70fc5dcc0ec64e076391576be29da1cce88f7c5cf725c31418601e4eee8fa354
> docker: a3a301693db0eea5af1278535586e7f9768bd497231d6748f35a983962780371
>
> 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.21.1-src.tar.gz | \
> cut -d ' ' -f1) \
> <(cat apache-druid-0.21.1-src.tar.gz.sha512 ; echo)
>
> diff <(shasum -a512 apache-druid-0.21.1-bin.tar.gz | \
> cut -d ' ' -f1) \
> <(cat apache-druid-0.21.1-bin.tar.gz.sha512 ; echo)
>
> Verify signatures:
> gpg --verify apache-druid-0.21.1-src.tar.gz.asc \
> apache-druid-0.21.1-src.tar.gz
>
> gpg --verify apache-druid-0.21.1-bin.tar.gz.asc \
> apache-druid-0.21.1-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.21.1
> [ ] 0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Thanks!
>

Reply via email to