In the process of verifying the release, it looks like the docker-compose.yml that we package is pointing to 0.22.0. I've raised https://github.com/apache/druid/pull/12618 to fix this.
Thanks, Atul On Wed, Jun 8, 2022 at 7:25 AM Kashif Faraz <kfa...@apache.org> wrote: > +1 > > verified: > - gpg signature > - shasum > - building the source artifacts (tests skipped) > - rat license check > - running the binary > - basic sanity ingestion and query > > Thanks > Kashif Faraz > kfa...@apache.org > > > On Mon, Jun 6, 2022 at 1:00 PM Abhishek Agarwal <abhishek.agar...@imply.io > > > wrote: > > > Hi all, > > I have created a build for Apache Druid 0.23.0, release candidate 1. > > > > Thanks to everyone who has helped contribute to the release. You can read > > the draft release notes here: > > https://github.com/apache/druid/issues/12510 > > > > The release candidate has been tagged in GitHub as druid-0.23.0-rc1 > > (efa67c4eddb31dc6e9ff7d0c070b9d1b1bf10a45), available here: > > https://github.com/apache/druid/tree/druid-0.23.0-rc1 > > > > The artifacts to be voted on are located here: > > https://dist.apache.org/repos/dist/dev/druid/0.23.0-rc1/ > > > > A staged Maven repository is available for review at: > > https://repository.apache.org/content/repositories/orgapachedruid-1029/ > > > > Staged druid.apache.org website documentation is available here: > > https://druid.staged.apache.org/docs/0.23.0/design/index.html > > > > A Docker image containing the binary of the release candidate can be > > retrieved via: > > docker pull apache/druid:0.23.0-rc1 > > > > artifact checksums > > src: > > > > > a8b8124297f4fb954d8f3cb79cf2ea867a689fe8d8b2470718d0d95badcd9e66d3658efcb064c50617b5ea4cbfbc3e650b01d742de7bc7b39050b1ba5da6b068 > > > > bin: > > > > > da1e0703db699fa523b7fa86b57eec5f77aa0b4141bee44324d81d5c8058a414bc896145f3dd7f5e12320593055e20b551ce597628de133a062d091e40c38a54 > > > > docker (sha256): > > 510c9be199d6b8568c62c6d4bcf1bb3c98690baf9521eccf8c6b335e90eeef97 > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/abhishek > > 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.23.0-src.tar.gz | cut -d ' ' -f1) > <(cat > > apache-druid-0.23.0-src.tar.gz.sha512 ; echo) > > > > diff <(shasum -a512 apache-druid-0.23.0-bin.tar.gz | cut -d ' ' -f1) > <(cat > > apache-druid-0.23.0-bin.tar.gz.sha512 ; echo) > > > > Verify signatures: > > gpg --verify apache-druid-0.23.0-src.tar.gz.asc \ > > apache-druid-0.23.0-src.tar.gz > > > > gpg --verify apache-druid-0.23.0-bin.tar.gz.asc \ > > apache-druid-0.23.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.23.0 > > [ ] 0 I don't feel strongly about it, but I'm okay with the release > > [ ] -1 Do not release this package because... > > > > Thanks! > > >
