+1 (binding)

src package:
* verified checksum and signature
* rat check successful
* checked for LICENSE and NOTICE
* built binary distribution, ran batch ingestion and some queries

binary package:
* verified checksum and signature
* ran ingestion(native/MSQ), and some queries
* checked for LICENSE and NOTICE

docker:
* started cluster with docker-compose, ran some batch ingestion/queries

On Fri, Jan 31, 2025 at 2:14 PM Adarsh Sanjeev <adarshsanj...@apache.org>
wrote:

> Hi all,
>
> I have created a build for Apache Druid 32.0.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/17677
>
> The release candidate has been tagged in GitHub as druid-32.0.0-rc1
> (960e85112c89304a6f7e2ac64b2ba3b453743346), available here:
> https://github.com/apache/druid/releases/tag/druid-32.0.0-rc1
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/druid/32.0.0-rc1/
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachedruid-1082/
>
> Staged druid.apache.org website documentation is available here:
> https://druid.staged.apache.org/docs/32.0.0/design/index.html
>
> A Docker image containing the binary of the release candidate can be
> retrieved via:
> docker pull apache/druid:32.0.0-rc1
>
> artifact checksums
> src:
>
> 171f80facaefaaa6c0e91f972d486582894b882e7e0c2c742b0621eea197e52177243d0a358144961cba93f5363565b559c3d908bc7e285652ca620d7ebef916
> bin:
>
> cb06be6e567104459d04d79feb46dbaa51f8a77e3248221a5df7be98d7753da1fe9b234c219d8238bdfbb1e77732904758493b1c433de38c3fd70855606d8e56
> docker: 44c8015c8bb2c861cf09fb0de886d9e3747b3acb70f53fe33e8e884bf6545877
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/adarshsanjeev.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-32.0.0-src.tar.gz | cut -d ' ' -f1)
> <(cat apache-druid-32.0.0-src.tar.gz.sha512 ; echo)
> diff <(shasum -a512 apache-druid-32.0.0-bin.tar.gz | cut -d ' ' -f1)
> <(cat apache-druid-32.0.0-bin.tar.gz.sha512 ; echo)
>
> Verify signatures:
> gpg --verify apache-druid-32.0.0-src.tar.gz.asc apache-druid-32.0.0
> -src.tar.gz
> gpg --verify apache-druid-32.0.0-bin.tar.gz.asc apache-druid-32.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 32.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!
>

Reply via email to